nextcloud
[Bug]: Win desktop app (3.14.1) crashes right after starting before synchronizing any files
⚠️ 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
Nextcloud desktop app (Nextcloud-3.14.1-x64) crashes right after start before synchronizing any files. This error was present in the previous version 3.13 but even older version 3.9.3 works just fine.
Steps to reproduce
Start the desktop application. No other action necessary for the crash to occur. The crash does not occur when computer is not connected to the internet.
Expected behavior
It does not crash.
Which files are affected by this bug
N/A
Operating system
Windows
Which version of the operating system you are running.
Windows 10 22H2 OS build 19045.5011 Windows Feature Experience Pack 1000.19060.1000.0
Package
Official Windows MSI
Nextcloud Server version
30.0.0
Nextcloud Desktop Client version
3.14.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
Only this, repeated: {"reqId":"ScXU5Iqnn06yICxxQ1kM","level":3,"time":"2024-10-12T07:26:22+00:00","remoteAddr":"77.90.22.35","user":"--","app":"no app in context","method":"GET","url":"/login.asp","message":"Capabilities of OCA\Richdocuments\Capabilities took 1.31 seconds to generate.","userAgent":"--","version":"30.0.0.14","data":[]}
Additional info
Windows event log:
Faulting application name: nextcloud.exe, version: 3.14.1.55839, time stamp: 0x66f6776f Faulting module name: ntdll.dll, version: 10.0.19041.5007, time stamp: 0x688f8c4b Exception code: 0xc0000005 Fault offset: 0x0000000000079db0 Faulting process ID: 0x104 Faulting application start time: 0x01db1c766f131cd2 Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: 9625f37c-c1a0-43ee-b9a4-cf029ce2c280 Faulting package full name: Faulting package-relative application ID:
App log: 20241012_0926_nextcloud.log
I have similar problem with that.
I formatted my pc today. When I installed the program in several times I can't run it. The program should minimize to tray and stay any icon, but the program doesn't run.
I tried install several times after. I tried installing .net libraries, ... but I can't launch it.
Thanks.
PD: Sorry for my English
Same issue here on one windows 11 pc too, downgraded to 3.13.4 and sync works again without crash
Yes, I encountered the same problem in version 3.14.1. When I modify a file on one computer, the other computer will crash immediately when it synchronizes the modifications. But if I delete this file and let this computer pull it back, it won't crash.
Same problem for me, downgrading to 3.13.4 does not stop the problem. The problem seems to be as said in the start of the syncing process, when starting the client without a internet connection or with a paused sync everything works until you start the sync process. Using Win11 and nothing in the event manager.
Had to force a few times the new sync process to get it working in v3.13.4
The server log provides a ton of "Computed md5 hash is incorrect." failures:
"app": "no app in context",
"method": "POST",
"url": "/remote.php/dav/bulk",
"message": "Computed md5 hash is incorrect.",
"userAgent": "Mozilla/5.0 (Windows) mirall/3.13.3stable-Win64 (build 20240823) (Nextcloud, windows-10.0.22631 ClientArchitecture: x86_64 OsArchitecture: x86_64)",
"version": "29.0.7.1",
I also have the same problem. After my simple test：
3.14.1and3.14.2: crashed3.13.3and3.13.2: appear unresponsive
I suspect it is caused by too many small files, because I encountered a similar problem in 3.13.3. At that time, I deleted tens of thousands of pictures and the synchronization returned to normal. But the current situation is that I did not have a one-time Synchronizing too many files can also cause this problem.
我也有相同的问题。经过我简单的测试，3.14.1和3.14.2的表现为闪退，而3.13.3和3.13.2表现为无响应。我怀疑是小文件过多引起的，因为在3.13.3的时候我遇到过相似的问题，当时我把几万张图片删除后同步就恢复了正常，但现在的情况是我并没有一次性同步太多文件也会导致该问题。
I also have the same problem. After my simple test：
3.14.1and3.14.2: crashed3.13.3and3.13.2: appear unresponsiveI suspect it is caused by too many small files, because I encountered a similar problem in
3.13.3. At that time, I deleted tens of thousands of pictures and the synchronization returned to normal. But the current situation is that I did not have a one-time Synchronizing too many files can also cause this problem.我也有相同的问题。经过我简单的测试，3.14.1和3.14.2的表现为闪退，而3.13.3和3.13.2表现为无响应。我怀疑是小文件过多引起的，因为在3.13.3的时候我遇到过相似的问题，当时我把几万张图片删除后同步就恢复了正常，但现在的情况是我并没有一次性同步太多文件也会导致该问题。
It seen everthing is ok when I turn off the tun mode（NextCloud Desktop version is 3.13.3）
Experiencing v3.14.0-3 clients all crashing on multiple Windows 10 Pro 22H2 machines with latest OS updates installed on them.
v3.13.4 meanwhile works on all systems.
Unfortunately turning off auto update in the client still results in Nextcloud offering updates to v3.14 upon each start and thus some users just update to it again. Cleaning app cash after turning off auto update does not fix this issue.
That is, v3.14.X is still not reliable on Win 10 after almost 2 months since it's original release.
p.s. if anyone knows how to reliably fully turn off auto update function after reverting to v3.13.4 please let me know
Simple unchecking auto updates in GUI works. You should also delete already downloaded installation files from C:\Users<username>\AppData\Roaming\Nextcloud
In my test:
- Win11 23H2
- Win11 24H2
- Win10 22H2
I found that the Windows version does not matter. The important part is the System Locate (in Region Settings).
If your setting is not English (XXX), you will occur this issue. Or you can enable the UTF-8 support to suppress this issue but in my experience, enabling this beta feature may cause the other problem in other programs.
I think this is a classic Unicode issue, but the old versions (<=3.13.4) will not occur.
@karlisi thank you, will check the directory you’ve mentioned for installation files. Clearing Nextcloud cache with CCleaner did not fix the update dialog on program start.
@Ami-OS thank you for sharing your findings. Will try setting language to English.
What’s the deal though with this unicode support? Why does v3.13.X does not have the issue, while v3.14.X apps quit? Is it something that Nextcloud developers can fix and take into account in the future to avoid possible problems?
Last year I think there was a bug related to unicode, when any file names containing anything outside ASCII symbol set failed to sync. It was a widespread issues which was fixed in just 3 or 4 days.
This problem however is two months old… and no real fix in sight?
I can confirm, it should be unicode related. I have non English system locale set. If synchronizing file with non-english characters in it's name from server, client crashes. After I rename it to all english characters, using web interface, synchronization is ok.
The problem seems to be related to the depth of the path, and the program crashes if the path is too long.
@Touseall In my test case, the short path has same issues. Do you have any non-english characters in your test case?
@Touseall I had very short path, less than 50 characters, including disk name and filename extension
@karlisi thank you, will check the directory you’ve mentioned for installation files. Clearing Nextcloud cache with CCleaner did not fix the update dialog on program start.
@Ami-OS thank you for sharing your findings. Will try setting language to English.
What’s the deal though with this unicode support? Why does v3.13.X does not have the issue, while v3.14.X apps quit? Is it something that Nextcloud developers can fix and take into account in the future to avoid possible problems?
Last year I think there was a bug related to unicode, when any file names containing anything outside ASCII symbol set failed to sync. It was a widespread issues which was fixed in just 3 or 4 days.
This problem however is two months old… and no real fix in sight?
@karlisi thank you, will check the directory you’ve mentioned for installation files. Clearing Nextcloud cache with CCleaner did not fix the update dialog on program start.
@Ami-OS thank you for sharing your findings. Will try setting language to English.
What’s the deal though with this unicode support? Why does v3.13.X does not have the issue, while v3.14.X apps quit? Is it something that Nextcloud developers can fix and take into account in the future to avoid possible problems?
Last year I think there was a bug related to unicode, when any file names containing anything outside ASCII symbol set failed to sync. It was a widespread issues which was fixed in just 3 or 4 days.
This problem however is two months old… and no real fix in sight?
It has been two months since the crash and incorrect display of the local language, and an iterative version has not yet been released to fix these two serious issues. It's really regrettable!
System display language setting to English but System Locate not will also lead to this problem especially there are huge numbers of files waiting to be uploaded
@laoxong Since display language does not affect the system character encoding (System Locate), and vice versa.
Tested version 3.15. No changes, desktop client crashes on files with non-english characters in filename.
Done some research, here are my observations. Created file rūķīši.txt (non-english characters) in web interface, put some text in. Text in english only. Client crashed. Renamed file to rukisi.txt (only english characters) in web interface, this time sync ok. Edited file content in web interface, sync ok, as expected. Renamed back to rūķīši.txt (non-english characters) in web interface, sync ok. Very interesting. Edited again file content in web interface, this time client crashed.
Tried the same operations from client side, sync was ok, no matter of filename or content.
User locale Latvian, display language English (doesn't matter), system locale Latvian.
FYI I checked two log files that likely correspond to crashes and they both end with this:
2024-12-03 23:04:10:655 [ info nextcloud.gui.application C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\gui\owncloudgui.cpp:251 ]: Sync state changed for folder "REDACTED" : "Sync running"
2024-12-03 23:04:10:657 [ info nextcloud.sync.propagator C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\libsync\owncloudpropagator.h:221 ]: Starting CSyncEnums::CSYNC_INSTRUCTION_SYNC propagation of "REDACTED CHINESE TEXT 中文" by OCC::PropagateDownloadFile(0x1af63726270)
2024-12-03 23:04:10:657 [ warning nextcloud.sync.vfs.cfapi.wrapper C:\Users\User\AppData\Local\Temp\windows-27030\client-building\desktop\src\libsync\vfs\cfapi\cfapiwrapper.cpp:784 ]: empty path
Has any developers noticed this issue? All versions after 3.14.1 have this problem, look forward to its fix
Version 3.15.3 fixed non-english filename problem (bug https://github.com/nextcloud/desktop/issues/7258). If You have this version and crashes, perhaps that's another issue