[Bug]: Desktop client fills all available memory and crashes after Steam client is launched

### ⚠️ 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

Under certain conditions the Nextcloud desktop client fills all available memory and then eventually crashes.

### Steps to reproduce

1. Launch Nextcloud desktop client
2. The client is in the process of uploading files or checking for changes in remote
3. Launch the Steam client
4. Nextcloud desktop client stops responding and starts using all available memory until it crashes


### Expected behavior

The Nextcloud doesn't use excessive memory, stays responsive and doesn't crash.

### Which files are affected by this bug

No files affected

### Operating system

Linux

### Which version of the operating system you are running.

Manjaro Stable 2022-06-12

### Package

Distro package manager

### Nextcloud Server version

24.0.1 (snap)

### Nextcloud Desktop Client version

3.5.1

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

Fresh desktop client install

### 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

The Steam client is `steam-native` [package](https://software.manjaro.org/package/steam-native), version `1.0.0.70-2`
When exiting Steam, the memory leak continues.
When Steam client is launched first and then Nextcloud client, the issue does not occur.

Unfortunately can't include the desktop client logs because of too much sensitive data.