[Bug]: Version 3.15.n seems to be stuck in an infinite loop during "Checking folder changes". HDD is running hot.
⚠️ 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 and Desktop Releases for supported versions.
- [x] I agree to follow Nextcloud's Code of Conduct
Bug description
Debian 12 Linux, Gnome DE, Nextcloud Desktop client 3.15.0
Version 3.15.0 seems to be stuck in an infinite loop during "Checking folder changes". HDD is running hot. I've let it run for 30 minutes and more, just to see if it eventually stops at some point. It doesn't.
General startup of the client seems fine. File sync runs through fine. After that it goes into "Checking folder changes" - that's where it gets stuck in the loop. Reaction times get very slow on every action I take in the client. Gnome offers generic "App not responding, should I kill it or wait" warning. With every older Client (e.g. 3.14.3) it works just fine. So there seems to be some regression introduced in 3.15.0...
Edit: seems to be related to the fact, that there is a NTFS partition involved...
If there's any more info I can provide, please let me know.
Steps to reproduce
Startup Nextcloud-3.15.0-x86_64.AppImage Wait for the app to start up...
Expected behavior
normal startup without trashing my HDD...
Which files are affected by this bug
folder
Operating system
Linux
Which version of the operating system you are running.
Debian 12
Package
Official Linux AppImage
Nextcloud Server version
30.0.3
Nextcloud Desktop Client version
3.15.0
Is this bug present after an update or on a fresh install?
Updated to a major version (3.14.3 to 3.15.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
Seems to be internal Desktop Client issue
Additional info
No response
I have the same issue on arch linux also with gnome. My nextcloud folder is located on a ntfs drive (windows dual boot) and mounted using ntfs-3g. I've reverted to 3.14.3 and everything worked again
Im also running on a NTFS drive! Funny, didn't think of that! Thanks for the input!
Same issue with NTFS partition on Arch Linux when using 3.15.0 3.14.3 works fine
Same Problem on Linux Mint 22 Cinnamon with 3.15 Flatpak
Hope this will fixed fast.
Can confirm I experience the same issues running 3.15.2 on Arch using KDE, ext4 formatted drives.
I tried downgrading to 3.14.3 but the problem still persists. If I restart nextcloud it will sync fine until I change a file - then it hangs.
I am also experiencing the same hanging issue on Arch Linux with only ext4 formatted drives. Downgrading to 3.14.1 seems to resolve the issue, but every version after that one leads to UI hangs and seemingly indefinite CPU usage for me. It sounds like the issue only cropped up after 3.14.3 for some users, but I definitely see the same issue with that build, and it sounds like some others here also still saw issues with 3.14.3.
If others here could confirm whether 3.14.1 does or doesn't show the same issue, that might help bisect the issue.
3.13.4 Appimage is running on my Linux Mint 22 the last, that runs normal. 3.14 is not startable as an Appimage - wants passwords busshit 3.15.2 als flatpak (normal i use flatpak) has also the bug that it syncs all time, despite nothing is changed on the file system. 3.14.x as flatpak had run fine. 3.15.x brought the bug
Just updated on arch... Same result. CPU 100%, flooding logs.
I already deleted package cache. How I can download previous version at arch linux? On mirror is already new version.
Check the arch linux archive for prior versions: https://archive.archlinux.org/
Check the arch linux archive for prior versions: https://archive.archlinux.org/
Thanks https://archive.archlinux.org/repos/2024/11/09/extra/os/x86_64/nextcloud-client-2%3A3.14.3-1-x86_64.pkg.tar.zst
I tried to compile it from sources, but after hour it seg faulted in some test
I am also experiencing the same hanging issue on Arch Linux with only ext4 formatted drives. Downgrading to 3.14.1 seems to resolve the issue, but every version after that one leads to UI hangs and seemingly indefinite CPU usage for me. It sounds like the issue only cropped up after 3.14.3 for some users, but I definitely see the same issue with that build, and it sounds like some others here also still saw issues with 3.14.3.
If others here could confirm whether 3.14.1 does or doesn't show the same issue, that might help bisect the issue.
This did not resolve the issue for me.
I did some testing. I find that if I create an empty file (touch foo for example) in the Nextcloud root folder or in a folder with fewer files there is no issue. However, if I create a file in a specific folder (a 130 GB one with many files and git repos) Nextcloud hangs as described by this issue.
I can confirm the problem (on Debian sid using 3.15.0). My nextcloud folder is also on an NTFS partition and after the upgrade I saw a high CPU load of the nextcloud binary and the ntfs-3g fuse driver. I ran git bisect which showed 5b2af166d3d9c8537c565922750392d4a3f6610e as the first faulty commit. I suppose that trying to apply the file permissions does not work on NTFS so nextcloud tries it over and over again.
@mgallien ^ can you please have a look
I've rebuilt 3.15.2 with 5b2af166d3d9c8537c565922750392d4a3f6610e reverted and nextcloud-desktop is working properly again.
Very nice! Now let's hope that someone from Nextcloud ever sees this and puts this to work. Thanks a lot.
I'd love to put a thumbs up or sth, but github won't let me in anymore since I stupidly activated 2 factor auth. Microsoft is very actively involved in locking people out...
Anyway! Good work! And thanks!
For completeness sake, the NTFS partition is mounted like this:
$ grep data /etc/fstab
LABEL=Data /mnt/data ntfs-3g auto 0 0
$ findmnt /mnt/data
TARGET SOURCE FSTYPE OPTIONS
/mnt/data /dev/nvme0n1p11 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
I have the same issues using the same account in two different systems having the latest nextcloud client. htop reports 100% CPU while the UI is unresponsive. I have had this behavior in debian and arch linux.
My account has around 150000 files
This causes disk IO on my desktop to run Debian, as I can hear the drive needle of my HDD working. In Debian, the system is NTFS. In my laptop running arch I am using ext4 storage and get the same behavior. This drains the battery of my laptop and causes it to run hot.
To make things worse, the service was auto spawned from the bus service, and I could not even kill the client without it restarting.
Can you please tell us what information we need to upload to get help with this issue?
I've filed a downstream bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091614 and the Debian maintainer was so kind to revert the problematic commit in the Debian package until a proper fix is found.
3.15.50 version from daily channel still has this bug. (OS: Linux Mint 22)
I've filed a downstream bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091614 and the Debian maintainer was so kind to revert the problematic commit in the Debian package until a proper fix is found.
Is possible do that same for other distros too?
Everytime when I update arch I have to downgrade afterwards nextcloud client, mostly I remember right after 100% cpu and battery drain after 1 hour instead 6h.
For the record: Version 3.15.3 still has the same issue...
I'm glad to see some movement! Thanks!
@chris-blues if you can, could you test the AppImage once ready within https://github.com/nextcloud/desktop/pull/7745 ? should have the fix
No problem. Does it appear later on that page?
Edit: Ok, got it. https://github.com/nextcloud/desktop/pull/7745#issuecomment-2582774542 It still seems to be stuck on "Checking folder changes". And I still hear the HDD working. But CPU usage has gone down. Both AppRun.wrapped and mount.ntfs go with ca 20% CPU usage. I'll let it do it's thing and wait, if it stops...
Edit 2: Naa, CPU usage goes between 20 and 100%... UI grows very slow and laggy.
I can confirm. The AppImage still shows the same buggy behaviour
I can confirm. The AppImage still shows the same buggy behaviour
My NTFS file system type is reported as fuseblk , not NTFS
I can confirm. The AppImage still shows the same buggy behaviour
My NTFS file system type is reported as
fuseblk, notNTFS
Also fuseblk can be anything baded on FUSE.
Like sshfs, ftpfs, webdavfs, etc...