Updated to Nextcloud Desktop Client 33.0.0 this morning, and I’ve now been seeing consistenly high memory usage (~5GB) while idle.
This hasn’t happened on previous version or even today before updating, the Nextcloud server hasn’t had anything changed since updating, so I’m not sure what’s going on.
Steps to replicate:
Install Nextcloud Client 33.0.0
Add an account to sync
High memory usage
Info
Nextcloud Server version (e.g., 29.x.x) :
Operating system and version (e.g., Ubuntu 24.04) :
Reverse proxy and version _(e.g. nginx 1.27.2)
Is this the first time you’ve seen this error? (Yes / No):
When did this problem seem to first start?
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Update, turning off “Use System Proxy” for my connection clears out all the memory, and then memory usage slowly increases over time again, no matter if I leave it on “No proxy” or “Use System Proxy”
Created a bug report for this as it seems to be an issue with the Desktop Client and “Cookbook” app.
opened 07:01PM - 24 Mar 26 UTC
0. Needs triage
bug
os: Windows
### ⚠️ Before submitting, please verify the following: ⚠️
- [x] This is a **bug… **, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)
### Bug description
Having the cookbook extension enabled on a Nextcloud server which is having files synced via the Desktop Client causes the Desktop Client to leak memory.
It also causes consistent CPU usage (~4% on a Ryzen 7 5800X, plus additional usage from Windows Defender scanning the created log files) , disk usage (~1.5MB/s, presumably writing to logs), and network usage (~120KB/s)
See image for resource usage with this bug. Note, the memory usage continues to increase (I've seen it as high as 7GB)
<img width="722" height="82" alt="Image" src="https://github.com/user-attachments/assets/d7b3b832-2a65-4a0a-a300-32ffb4b2cb04" />
### Steps to reproduce
1. Enable [Cookbook](https://apps.nextcloud.com/apps/cookbook) on a Nextcloud server
2. Ensure a folder is being synced via the Desktop Client
3. Switch from "No proxy" to "Use system proxy" (without this, it may not work from just installing the app, this seems to refresh something)
4. Wait for memory usage to slowly increase.
### Expected behavior
No memory leak, this app doesn't sync anything to desktop anyways.
See image for usual Desktop Client resource usage
<img width="721" height="83" alt="Image" src="https://github.com/user-attachments/assets/c2819225-b99d-462c-b794-933fa950823b" />
### Which files are affected by this bug
gui\creds\webflowcredentials.cpp, src\libsync\accessmanager.cpp
### Operating system
Windows
### Which version of the operating system you are running.
Windows 10
### Package
Official Windows MSI
### Nextcloud Server version
32.0.6
### Nextcloud Desktop Client version
33.0.0
### Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 3.16.3 to 3.17.0)
### Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
### Are you using an external user-backend?
- [x] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Nextcloud Server logs
```shell
There are no server logs from around the time that this bug occurs.
```
### Additional info
Switching from "No proxy" to "Use system proxy" (or vice verca) clears the memory used,
I've only attached a portion of the desktop logs, as it is the same thing for over 39k lines, over the span of 4 minutes.
[log_upload.log](https://github.com/user-attachments/files/26223834/log_upload.log)
1 Like
Same issue here. After 5 min my client is using 4 gb of ram and slowly increase the usage each second
Rello
March 25, 2026, 5:25pm
6
Hello,
problem was located already and is in progress
2 Likes