Closed Keagel closed 1 month ago
This seems to be caused by virtual files support. Completely disabled that option and it's now syncing again.
Hello,
thank you for reporting this issue.
This issue was reported long time ago on old versions and we improved a lot since then. If the error shows up again, please open an issue for the current versions.
⚠️ Before submitting, please verify the following: ⚠️
Bug description
Application crashes during sync
Steps to reproduce
Expected behavior
Application shouldn't crash
Which files are affected by this bug
YXIy2PFarOexj8rvlVXyFWuQsSmDA195u2jPBV3dSefhWP5hKXsoBMTLURdmhlTLKSq1J8ls6hqg7sADWJlH1zNTchXvvl3xWjrMiopdqfdfX9X10QNdTlqNXjR7zR0uTka3PnhIigt2RIhCXWUCm3hpBJqcYBXYDKWZjxEiy9wIJYuGpheQFymNiu2t7NJI3kZMtQhHTEA1V0vGwhYBGfDp8kZCLpVqoWALpD9JUv5i1VHjBjbhbcelv
Operating system
Windows
Which version of the operating system you are running.
Windows 10
Package
Other
Nextcloud Server version
24.0.1
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?
Nextcloud Server logs
Additional info
If I remember correctly the client didn't crash from creating those files with long names, but the issue appeared after. The files have since been removed. I have also removed the .db files from my Nextcloud sync folder so that shouldn't cause issues anymore.
I've attempted to check the log files but I don't see any errors in there. Windows Event Viewer reports the same crash every time:
I've also started Nextcloud from the command line using these arguments:
"C:\Program Files\Nextcloud\nextcloud.exe" --logfile C:\log\debug.log --logdebug
Resulting log is very large (> 200 MB) and stops being written to 2-3 minutes before the crash happens, so there is nothing of importance in there. I've observed the sync process from the Nextcloud window (I have a video). Syncing goes very fast for the first few thousand files. At some point the client freezes, I assume getting stuck on a file (simple very small image) for almost two minutes - then for a split second the client syncs that file and closes instantly.