[Bug]: Request used more than 300 MB of RAM: 288 MB
Open
@joshtrichards is already working on this.
Since Feb 3, 2026.
0. Needs triage
32-feedback
bug
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
I have a warning in my logging panel which says:
Request used more than 300 MB of RAM: 288 MB
Which is weird, because I consider 288 MB to be less than 300 MB.
Steps to reproduce
This issue is hard to reproduce as this warning occurs infrequently.
Expected behavior
I expect the warning to not show up or show up with numerical values in which the request in fact used more than 300 MB of RAM.
Nextcloud Server version
32
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.4
Web server
Nginx
Database engine version
PostgreSQL
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?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
will provide if needed
List of activated Apps
will provide if needed
Nextcloud Signing status
No errors have been found.
Nextcloud Logs
{"reqId":"2E6BQ6CYBAdtnnQ1Zqd9","level":2,"time":"2026-02-03T10:40:55+00:00","remoteAddr":"153.96.47.6","user":"hermann","app":"core","method":"GET","url":"/settings/apps/update/richdocumentscode","scriptName":"/index.php","message":"Request used more than 300 MB of RAM: 288 MB","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0","version":"32.0.5.0","data":{"app":"core"},"id":"6981d3411c939"}
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.