[Bug]: Memory Leak on Linux with 3.13 client version

[RandomLegend]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Memory usage of the nextcloud-client application slowly creeps up in RAM usage until the system goes oom; Had my PC running and going for a walk, came back to it using 59GB of RAM (i have 64GB) and the system becoming completely unresponsive.

Steps to reproduce

1. Open and use the newest Nextcloud-Client for Linux (either from the arch extra repo or the git version from AUR / Chaotic-AUR
2. Observe it using as much RAM as it can get.

Expected behavior

It not using all the RAM

Which files are affected by this bug

No File but the basic application itself

Operating system

Linux

Which version of the operating system you are running.

Garuda Linux - 6.8.7-zen1-2-zen Kernel

Package

Distro package manager

Nextcloud Server version

28.0.4

Nextcloud Desktop Client version

3.13.0.r268.gaa175036e9-1 // 3.13

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

No response

Additional info

Downgrading to 3.12 stops the memory leak

[fermino]

Same issue on Arch Linux (6.6.29-1-lts). It seems to have been introduced somewhere in 3.13, as 3.12.3-2 does not exhibit the issue. If I have the time I will try to bisect it to find the offending commit.

[JackV2020]

Same issue with the 3.13 AppImage on Ubuntu 20.04.6 LTS.
I have an old laptop with 8GB memory so hardly had the chance to stop the client after auto startup.
I put 3.12 back in place and everything works fine again.

[leucome]

Same on Manjaro. At some point my computer was struggling then I looked and Nextcloud was using all the ram + all the swap. So I downgraded to 3.12 and it's working fine.

I noticed this just after upgrading to Manjaro 24 with Plasma 6 and stuff. Not sure If Nextcloud 3.13 was updated at same time. It might be a bit hard to nail down the change causing this because there was a lot of change in one update.

[laurent4net]

Same issue on Arch Linux with NextCloud 29 server and client 3.13.0
20GB RAM used in less than 20min and client killed by OOM. Repeated 3 times.