-
Notifications
You must be signed in to change notification settings - Fork 241
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
Memory consumption since upgrade to 25.0.11 #5479
Comments
I forgot to add that the users facing the errors 500 are the heavy users of Calendar. Those with just a few events doesn't suffer from the issue. |
Possible duplicate of #5476 with the same problem but different symptoms. |
Just for the sake of exhaustivity, I'm experiencing the same issue (error 500 for some users) on a fresh install of NC 27.1.1 (on the same data). |
Can I help in any way pinpoint the culprit? |
If you update to Calendar 4.5.2 the feature that caused the heavy load has been reverted so it should work fine again. |
I can confirm that version 4.5.2 is no more affected by this issue. |
Closing this then :) |
Steps to reproduce
After upgrading to 25.0.11, some users are unable to use the Calendar webUI. Event previews on the homepage or CalDAV is still working fine for them. Only the WebUI is unavailable (Error 500).
Expected behavior
The WebUI should show for every user.
Actual behaviour
For those users, going to their calendar only triggers an error 500 with a blank page.
Calendar app version
4.5.0
CalDAV-clients used
No response
Browser
Firefox/117.0 or /102
Client operating system
debian, ubuntu
Server operating system
Debian
Web server
Nginx
Database engine version
PostgreSQL
PHP engine version
PHP 7.4
Nextcloud version
25.0.11
Updated from an older installed version or fresh install
Updated from an older version
List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
No response
Additional info
I tried to increase the php memory_limit from the recommended 512M value. Only increasing the limit to 1G was able to circumvent the issue (but this can't be a sensible solution, can it?).
The text was updated successfully, but these errors were encountered: