-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Visiting settings/admin/logging consumes CPU/RAM and triggers out of memory crash when Live is on #1262
Comments
this is still happening in 29.0.3 just visiting logging page will immediately ramp up CPU fan and load. |
The freezing/crashing does not happen to me any longer, since the update to 29.0.4. Can someone cross-check? |
It is still happening with NC 29.0.4 on FF on my side... |
No freezes on Chrome (127.0.6533.73), Firefox (128.0) or Safari on my side. That's weird. |
FWIW, this has been a problem for me on two different NC installations: AIO on Debian; straight install on Ubuntu. And its been happening at least since 29.0.3 and possibly before (currently: the AIO is 29.0.4 and the other is 29.0.6). I've mostly tested with Firefox 115.14.0esr and a little chrome 128.0.6613.119. The tab will freezes up either immediately or after some use, and sometimes the whole window freezes. On occasions parts of the window are clickable and parts are not, even outside of the tab. |
I tried to analyze this problem a bit more today, and I maybe have a clue. It doesn't freeze systematically, but when it does, this is because the |
I am experiencing the same bug. As usual, it appears to be nextcloud making some kind of enormous memory allocation. This has been happening since at least (from memory NC26, and persists in the current version (29.0.7 at the time of writing). The logging page (when it has worked) has always been incredibly slow and prone to crashing my browser (often taking down my entire laptop - I'm not rich and havent got much RAM.) In spite of being lowish on RAM, No other website I browse is this abysmally sluggish, and I can normally have over 50 tabs open on the machine on various sites. |
i experienced the same problem, restart apache2.service make off the problem, but reappear between 2-3 minutes after restarting |
still happening in nextcloud 30.0.1 RC1 |
Is your system generating lots of new log entries every second? Are the in-browser Log reader settings set to Debug perhaps? The Those reporting this matter:
Also, in case of interactions with browser extensions, try reproducing with extensions off (and maybe in private browsing mode) just to see if it changes behavior. |
Thanks @joshtrichards My log reader settings is set on the Warning level as well as the filters (Warning, Error, Fatal). The local time format is checked as well as the live view.I don't have a lot of entries over a one minute period, sometime only 2 or 3! As I said, the reader doesn't freeze systematically, but when it does it doesn't looks like a number of entries problem |
Reproduced, though I'm not sure how/what precisely triggers it at the moment. It more sort of just... started happening. |
I am not generating that many entries. Sometimes non per day. It also doesnt want to display the details of log entries. for me it always freezes almost immediately. I dont know what you mean by time format I use 24h clock system I really hope it can be debugged. |
Because of the above thread, I took another look at logging on two instances (AIO docker NC 29.0.4 and a stand alone NC 29.07). If I turn off Live-view/Polling in Log reader's settings, both of them seem to function without an issue. If I turn it back on again, the window freezes. |
Same here, turning on live view causes a run away thread and freezes tab. Turning it off resolves the crash. |
Seems fixed for me in 30.0.1 stable branch. |
Waiting for the docker images to update, currently using NC30.0.0. Will report back once the release is made. |
the crashes are now happening again. No idea why it worked for a brief while. |
Perhaps we need to introduce a delay in the live view polling. |
Still there in 30.0.2 Tested with Chrome and Firefox |
Still happens in 30.0.3 but not so fast as previous. I thought it was fixed, but no luck. |
This comment has been minimized.
This comment has been minimized.
Edge crashes almost immediately : RESULT_CODE_HUNG on 30.0.4. I am sorry, I am not a developer, I don't understand the problem or its complexity on why this is still a thing since May 2024. |
This is still happening on Chrome, Edge and Firefox for me as well, currently on Nextcloud 30.0.3. I noted a semi related ticket here which relates to Nextcloud implementing Vue, to remedy the issue but it still does not seem to have fixed the issue over all. |
Bug description
Visiting settings/admin/logging crashes Edge and Firefox.
You can scroll up and down a bit then CPU load increases dramatically. The size of the logfile is 26MB.
RAM usage increases by several GB in seconds
and then the browser tab crashes: "Out of Memory"
Firefox survives sometimes:
For temporary fix clearing the logfile helps.
Steps to reproduce
Expected behavior
No crashes.
Installation method
Community Web installer on a VPS or web space
Nextcloud Server version
29
Operating system
RHEL/CentOS
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: