-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[stable29] fix(cron): Log excess memory usage at debug and info levels #45843
Conversation
5654e19
to
6390e78
Compare
/update-3rdparty |
6390e78
to
4190d6a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐘
This comment has been minimized.
This comment has been minimized.
The log you posted will not happen in the future anymore, because |
4190d6a
to
fccd54b
Compare
Signed-off-by: Josh <josh.t.richards@gmail.com>
fccd54b
to
92fce66
Compare
Hi still seeing this on NC 29.0.4
|
Yes, the logging is legitimate. It's to catch large memory consumers. Report it to the recognize repo please, since that's the job that is using the memory in your case. |
In your sample the memory usage increased by 615MB and 550MB. Exactly the cases we want to log. 🤷 |
Backport of #45530
Warning, This backport's changes differ from the original and might be incomplete⚠️ Todo
Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.