Open gessel opened 1 year ago
I have the same issue, but not including Google Earth. On two separate windows clients (win11 pro, nextcloud client 3.6.2), as soon as I open it and start syncing it will do the same thing until the systems are unusable and require a reboot.
confirm on macos M2
definitely thrashing with RAM, using up to 4GB and 99.3% cpu looks like a memory leak, though it manages to free some memory sometimes. doesn't respond to anything anymore. happens while syncing.
My problem comes and goes with syncing a live google earth folder (cute way to keep it synced across devices, but doesn't work). As with similar reported issues, it seems to be an issue with a live directory and my guess is that it happens when the application owner of a synced directory does something to the files of that directory that the client doesn't understand and causes a runaway condition of some sort.
I realize this is a nearly uselessly vague description and bereft of useful debug info, but it seems to afflict "live" local directories like games or earth cache directories. These probably aren't good candidates for sync anyway, but it is possible the owner application detects a change and "fixes" it and then the client detects the change and "fixes" it back and forth, but only the nextcloud client seems to go crazy. This may be due to a more compute/memory intensive check process and might be kicking off check threads faster than they can resolve slowly burning up memory and CPU - max CPU might limit it but if the limit is max memory the result is generally going to be a locked system.
I rather think it's just too many files. I tried syncing my nextjs code and the same happened. Nextcloud now gone on my computer... Can't use that. Unreliable.
That could be - I have a directory hierarchy with 157,824 files that I tried to sync and couldn't. It doesn't kill memory though, just winds the fan up to max (CPU load), but .googleearth only has 663 items in it. If Google earth is not running, it syncs fine, but soon after starting google earth, NextCloud Client eats all RAM and the computer is unhappy.
Nextcloud can always take away all of my memories
I confirm. I had the exact same behavior. I just ugraded to latest Nextcloud-3.7.4-x86_64.AppImage. And now the programs is not responding anymore as soon as i open google earth.
⚠️ Before submitting, please verify the following: ⚠️
Bug description
The share dialog is looking incomplete. ... This is a duplicate report of #4646 - as the client and server are different and those fields are a big part of the reports, I'm creating this one for your documentation pleasure.
If Nextcloud Desktop Client is running and Google earth is launched (the google earth directory is partially synced, see details) then although the desktop client does not show that the folder is actively being synced, memory usage runs away and the client crashes or the system pushes swap so hard it becomes unusable.
Steps to reproduce
I suspect the cache folder upsets the client's filter routine which leaks memory. The folder might hold 315MB or so of data.
They're explicitly ignored:
and unselected.
Expected behavior
When clicking on the share dialog, share by e-mail should be an option. ... No crash, no crazy memory usage.
Which files are affected by this bug
none - files aren't actually synced, it is a desktop client problem
Operating system
Linux
Which version of the operating system you are running.
jammy Ubuntu 22.04.1 LTS
Package
Other
Nextcloud Server version
24.0.5
Nextcloud Desktop Client version
3.6.2
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 3.3.6 to 3.4.0)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
It would be very helpful to have an automatic redaction tool for log posts - usernames, IP addresses, filenames, directory paths. Hashing them could be sufficient, even unsalted, as rainbow table precomputes are unlikely to be worth the CPU, but it an awful lot of extremely sensitive data is bundled into the logs/debug archives.