-
Notifications
You must be signed in to change notification settings - Fork 263
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
cron runs into several out-of-memory issues after 25 upgrade #7495
Comments
T'is a bit hard to debug for we don't have the state anymore, and the exhaustion could happen anyplace. For mail appears most often, you might suspect it is on of the jobs happening there. |
@ChristophWurst @GretaD for your evaluation ^ |
Is this still happening? |
Cannot say, have no big instance to upgrade. |
Ah, I might have misread. So the problem happens directly after the upgrade and then never again? |
It actually comes back
I recently overread someone talking of memory leaks on Horde. Maybe this is related? cc @miaulalala |
had to update my last comment ^ |
From #6280
|
Bug description
cron.php runs long and eventually dies with "Allowed memory size … exhausted" after upgrade to NC 25 (RC1). This happens a couple time before it settles down and works as expected.
But, what might be broken by the jobs that were terminated?
Steps to reproduce
Expected behavior
Background job run nicely and do not cause memory exhaustion failures (with a sensible memory limit set of course – 512 MB in this case).
Installation method
No response
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: