[Bug]: nextcloud-desktop 4.0.1 may crash in Linux after massive chmod/chown/chgrp.

[agmartin2]

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

Hi,

In some of my boxes I have a shared area controlled by nextcloud (formerly by owncloud). Some users can write there and some can only read. To have common permissions/ownerships I use a cron.hourly rude script with massive (and mostly unconditional) chmod/chown/chgrp on area contents. This should not affect modification times.

However, in one of my boxes with 8GB RAM this leads to a nextcloud crash. When started from console, the only message is "Killed". Soon after the cron.daily run nextcloud starts using more and more memory until all available memory is used and nextcloud crashes. Crash does not happen in another box with the same structure but 16GB RAM instead of 8, although there is a temporary increase in memory usage.

I have modified the script to only act on files not already having the desired property and this makes nextcloud stop crashing (and work more smoothly, script should have been this way from the very beginning). However, the original buggy script seems to have triggered an actual problem in nextcloud-desktop. IMHO it may stress nextcloud, but never make it crash.

Using nextcloud-desktop 4.0.1-2 from Debian GNU/Linux.

Hope this helps,

Thanks,

...

Steps to reproduce

See body of the message.
...

Expected behavior

No crash even in this case.
...

Which files are affected by this bug

No particular file is affected, apart from nextcloud client itself.

Operating system

Linux

Which version of the operating system you are running.

Debian GNU/Linux unstable

Package

Distro package manager

Nextcloud Server version

31.0.8.1

Nextcloud Desktop Client version

4.0.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 Enabled

Are you using an external user-backend?

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

Nextcloud Server logs

Additional info

No response