-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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]: Used memory grew by more than 50 MB when executing job OCA\DAV\BackgroundJob\RefreshWebcalJob #46638
Comments
@miaulalala please triage. This could be fixed by your incremental sync PR. |
Yep pretty sure that is fixed when using an incremental sync. But I'm wondering why the calendar is synced every hour. @Markoise did you manually set a sync period for every hour? |
Yes, I did. |
Ok, that's fine - this will be fixed in Nextcloud 30, the job will be up to 99% faster. Are you ok to close? |
Sure. Thanks a lot. 🙂 |
I also get these messages in Nextcloud 30 Used memory grew by more than 50 MB when executing job OCA\DAV\BackgroundJob\RefreshWebcalJob (id: 74290, arguments: {“principaluri”: “principals/users/markus”, “uri”: “calendargooglecom-1”}): 113.7 MB (before: 51.3 MB) |
Nextcloud 30 and I get a bunch of these: |
@miaulalala Could you please reopen the issue? |
Sure thing Is your calendar a holiday subscription calendar or is it a regular calendar that changes a lot? |
In this case, it's my wife's Google calendar. But it doesn't change very much. Sometimes an appointment is moved, sometimes a new one is created. But that happens maybe once a day. The message in the log for this calendar appears every hour. Subscribed school vacation, football and public holiday calendars do not cause a log entry. |
Hm, it's interesting for sure. So, the sync interval provided by the subscription calendar is taken into account now, so the hourly message isn't really surprising if this is the provided sync interval; but I'm still suprised that the delta sync is not helping for your calendar subscription. Can you do an export of this calendar before and after the sync and use a diffing tool to check what exactly is different with those calendars? Please let me know what you find. |
Okay. I have compared two files. In both ICS files there are DTSTAMP= entries per appointment. Nothing else is different. The files are 966 kb in size and contain appointments from 2013 onwards. |
Yeah I think the export generates a new DTSTAMP. We ignore the DTSTAMP when doing a sync anyway, so that shouldn't lead to a write. Lemme think some more, maybe I can find a debug strategy that will tell us more. Are you opposed to patching your instance with some debug logging? |
If you tell me how to do it and if it has any other effects, I can do it. |
Bug description
This entry appears in the log every hour when a Google calendar is called up.
[cron] Warnung: Used memory grew by more than 50 MB when executing job OCA\DAV\BackgroundJob\RefreshWebcalJob (id: 74290, arguments: {"principaluri":"principals/users/markus","uri":"calendargooglecom-1"}): 119.6 MB (before: 58.6 MB)
von ? von -- um 19.07.2024, 12:31:43
Steps to reproduce
Subscribe to Google Calendar
Expected behavior
No entry in the log
Installation method
Community Manual installation with Archive
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
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: