desktop [Bug]: Crash when using external/non-default path (in 3.13.x, but 3.12.x okay)

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

After updating from version 3.12.3 to 3.13.0 client crash, when using external storage path for files. In my case on SD card. After downgrade to 3.12.4 it working OK.

Issue reported by another user here: https://github.com/nextcloud-releases/desktop/issues/9

Steps to reproduce

Set files path to external media (SD card)

Expected behavior

Client crash

Which files are affected by this bug

No files affected

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Other

Nextcloud Server version

24.0.4

Nextcloud Desktop Client version

3.13.0

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?

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

Nextcloud Server logs

No response

Additional info

No response

Apr 26 '24 19:04 matvit92

Can confirm, got a call today from someone on 3.13.0 experiencing the same problem, after downgrade to 3.12.4 everything worked fine again. Logs didn't say anything useful, the event viewer showed that nextcloud crashed within module ntdll with error code 0xc0000005.

Apr 29 '24 14:04 michael-r-elp

Same on my dad's machine: crashes with 3.13.0; works fine with 3.12.4; has the nextcloud storage on N:\, a mapped drive

Apr 29 '24 14:04 DavidS

Can confirm this behaviour in 3.13.0. I actually just signed up for this. ;-)

Apr 30 '24 12:04 CWRMTM

Confirm: USB SDD -> crash, same pc local HDD -> works Nothing in my logs.

May 02 '24 11:05 willie68

oh, that's interesting. local SSD(SATA) -> crashed on my PC.

May 02 '24 15:05 hdmr14

oh, that's interesting. local SSD(SATA) -> crashed on my PC.

Mapped in default directory?

May 02 '24 17:05 matvit92

oh, that's interesting. local SSD(SATA) -> crashed on my PC.

Mapped in default directory?

Ah, No. I've set up a mapping to 'H:\Nextcloud'. Sorry for any confusion.

May 03 '24 16:05 hdmr14

same issue, I thought this was related to a case insensitive issue as NextCloud is Case Sensative on the server but it maybe related to external media. I use a 12TB external HDD for our teams backup/media and its been crashing. I updated because files weren't updating prior.

May 05 '24 12:05 digimbyte

Same issue here, sync to external usb hdd will crash on 3.13.0, downgrade to 3.12.4 & sync works.

May 10 '24 22:05 haziqnorisham

Same issue, windows client 3.13 crashes. Downgrade to 3.12.5 is working again Nom de l’application défaillante nextcloud.exe, version : 3.13.0.55335, horodatage : 0x66280dc7 Nom du module défaillant : ntdll.dll, version : 10.0.22621.3374, horodatage : 0xeae8eecc Code d’exception : 0xc0000005

May 11 '24 15:05 pascal142

Tengo el mismo error,

May 12 '24 13:05 toniQva

Exact same problem here, windows 11, drive is an encrypted container mapped to X:
Downgrading to client 3.11.0 and it works again

May 22 '24 13:05 steinjo

Confirm I got the same problem Windows 10 + Sandisk external SSD on E: drive. But only one of my account made the app crash

May 23 '24 20:05 obriat

Same issue, windows client 3.13 crashes. Downgrade to 3.12.5 is working again. Windows 11 + External network drive on \network\example\

May 26 '24 22:05 git-ikeda

same issue here with client 3.13.0-x64 on win10 file directory hosted on a veracrypt container mounted to x:\

program starts up. task bar symbol shows up. you can even open the main window. sync process starts and after 1-4 files it crashes. the log files contained no significant error messages.

downgrade to 3.14.5-x64 solved the issue

Jun 03 '24 21:06 unddef

Also here Nexcloud client 3.13.0 crashes when using an encrypted drive

after a few seconds when synching with local sync drive being a Veracrypt-encrypted file container
happens with two nextcloud server instances (synchronization with both servers was working previously)
attempt to sync with unencrypted local drive works
Windows 11 (version 22H2)
Windows event viewer on local client shows Level: Error; Source: ApplicationError AppName: nextcloud.exe, AppVersion 3.13.0.55335 ModuleName: ntdll.dll, ModuleVersion 10.0.22621.3527

Jun 12 '24 06:06 ragsna

Same issue with crashing on both 3.13.1 or 3.13.0 . Drive is on SD Card. Runs for 30 seconds and then crashes. Currently running on 3.12.6 without issues. Windows 11.

Jul 04 '24 13:07 DcryptedCA

Confirm, the problem still persists with the version 3.13.1.

Jul 08 '24 13:07 matvit92

Windows client 3.13.1 also crashes again. Downgrade to 3.12.5 is working. Windows 11 + External network drive on \network\example\

Jul 09 '24 00:07 git-ikeda

After 3 months of silence from the development team, is there anything new?

Aug 05 '24 12:08 willie68

News?

Aug 29 '24 17:08 tigernero79

Is it possible that this bug still exists in release 3.13.x? and no one bothers or is there any solution? a bug that doesn't exist in version 3.12.x

Aug 31 '24 15:08 tigernero79

Last time I checked a 3.13.x patch a month ago or so, it was still there. I'll admit I've been reluctant to test more recently, as long as there is no news posted on this issue.

Aug 31 '24 15:08 CleyFaye

As me. On all my Devices I'm still on the latest 3.12, clicking all the time the "you have to update " box away.

Aug 31 '24 17:08 willie68

Confirm: USB SDD -> crash, same pc local HDD -> works

Is this truly specific to external drives or merely any non-default drives (e.g. anything other than C:\)?

Aug 31 '24 20:08 joshtrichards

Unfortunately, 0xc0000005 is a rather generic Windows error.

Is the log getting anything written to it just prior to these crashes?

Alternatively, try running the client from the command-line. I believe even on Windows you'll get the stdout/stderr output that one does on Linux when started in this way (I don't have my Windows box handy to confirm at the moment with certainty). (e.g. https://docs.nextcloud.com/desktop/3.14/troubleshooting.html#command-line)

If anyone experiencing this is able/willing, it would be interesting to see if this is reproducible on the 3.14.x RC. It's QT6 based so there's a possibility whatever this is is gone. DISCLAIMER: Pre-release software so use with a test account + folder and/or with good backups in-place. https://github.com/nextcloud/desktop/releases/tag/v3.14.0-rc1

Aug 31 '24 21:08 joshtrichards

Test on 3.14 rc1 but

would need the installation exe if possible I only see source code

Aug 31 '24 21:08 tigernero79

They are there: https://github.com/nextcloud-releases/desktop/releases

I'll run 3.14-rc1 for a bit and report back. It used to crash after less than a minute, so it should be easy to spot.

Aug 31 '24 21:08 CleyFaye

Yep. My situation is a synchronized directory in a veracrypt mounted drive (say "k:\syncdir"). The client did work (it added a file I created on nextcloud), but just crashed.

nextcloud --version says "3.13.81rc1-Win64" (I assume this is normal, as it also shows Qt6?).

Running nextcloud.exe --logwindow --logfile d:\nextcloud.log --logdebug ends on the following output:

2024-08-31 23:43:39:485 [ info nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\discovery.cpp:526 ]:	Processing "<some relative file path>" | (db/local/remote) | valid: true/true/true | mtime: 1725034756/1725034756/1725034756 | size: 122/122/122 | etag: "7147555642d41ce074a776bf106b7566"//"7147555642d41ce074a776bf106b7566" | checksum: "SHA1:6945a36bce1f38747feaa4dd355a9505e1a0f7fa"//"" | perm: "WDNVR"//"WDNVR" | fileid: "01107873oc1df7jsllrw"//"01107873oc1df7jsllrw" | type: CSyncEnums::ItemTypeFile/CSyncEnums::ItemTypeFile/CSyncEnums::ItemTypeFile | e2ee: false/false | e2eeMangledName: ""/"" | file lock: not locked//not locked | file lock type: ""//"0" | metadata missing: /false/
2024-08-31 23:43:39:485 [ debug nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\discovery.cpp:714 ]	[ OCC::ProcessDirectoryJob::processFileAnalyzeRemoteInfo ]:	item lock for: "<some relative file path>" OCC::SyncFileItem::LockStatus::UnlockedItem "" "" OCC::SyncFileItem::LockOwnerType::UserLock "" 0 0
2024-08-31 23:43:39:485 [ debug nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\discovery.cpp:1051 ]	[ OCC::ProcessDirectoryJob::processFileAnalyzeLocalInfo ]:	File "<some relative file path>" - servermodified: false noServerEntry: false
2024-08-31 23:43:39:486 [ debug nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\discovery.cpp:1745 ]	[ OCC::ProcessDirectoryJob::processFileFinalize ]:	"<some relative file path2> 0 0 0"
2024-08-31 23:43:39:486 [ info nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\discovery.cpp:526 ]:	Processing "<some relative file path>" | (db/local/remote) | valid: true/true/true | mtime: 1725140385/1725140386/1725140385 | size: 27/27/27 | etag: "e0e60d7e367e3fa3f9f62b43289c574e"//"e0e60d7e367e3fa3f9f62b43289c574e" | checksum: "SHA1:4c7957d92b45ed613795ac8ac7954dee12e7dd14"//"" | perm: "WDNVR"//"WDNVR" | fileid: "01107888oc1df7jsllrw"//"01107888oc1df7jsllrw" | type: CSyncEnums::ItemTypeFile/CSyncEnums::ItemTypeFile/CSyncEnums::ItemTypeFile | e2ee: false/false | e2eeMangledName: ""/"" | file lock: not locked//not locked | file lock type: ""//"0" | metadata missing: /false/
2024-08-31 23:43:39:486 [ debug nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\discovery.cpp:714 ]	[ OCC::ProcessDirectoryJob::processFileAnalyzeRemoteInfo ]:	item lock for: "<some relative file path2>" OCC::SyncFileItem::LockStatus::UnlockedItem "" "" OCC::SyncFileItem::LockOwnerType::UserLock "" 0 0
2024-08-31 23:43:39:486 [ debug nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\discovery.cpp:1051 ]	[ OCC::ProcessDirectoryJob::processFileAnalyzeLocalInfo ]:	File "<some relative file path>" - servermodified: false noServerEntry: false
2024-08-31 23:43:39:486 [ debug nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\discovery.cpp:1252 ]	[ OCC::ProcessDirectoryJob::processFileAnalyzeLocalInfo ]:	Local file was changed: File "<some newer relative file path>" item->_instruction: CSyncEnums::CSYNC_INSTRUCTION_SYNC noServerEntry: false item->_direction: OCC::SyncFileItem::Up item->_size: 27 item->_modtime: 1725140386
2024-08-31 23:43:39:486 [ info nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\discovery.cpp:1743 ]:	"<some newer relative file path> 64 1 0"
2024-08-31 23:43:39:486 [ info nextcloud.sync.engine C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\syncengine.cpp:783 ]:	#### Discovery end ####################################################  935 ms
2024-08-31 23:43:39:487 [ info nextcloud.sync.engine C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\syncengine.cpp:833 ]:	#### Reconcile (aboutToPropagate) ####################################################  935 ms
2024-08-31 23:43:39:487 [ info nextcloud.sync.statustracker C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\syncfilestatustracker.cpp:239 ]:	Investigating "Journal" OCC::SyncFileItem::NoStatus CSyncEnums::CSYNC_INSTRUCTION_UPDATE_METADATA OCC::SyncFileItem::Down
2024-08-31 23:43:39:487 [ debug nextcloud.gui.socketapi C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\socketapi\socketapi.cpp:228 ]	[ OCC::SocketListener::sendMessage ]:	Sending SocketAPI message --> "STATUS:OK:K:\\syncdir\\somepath" to QLocalSocket(0x1c91e8fc600)
2024-08-31 23:43:39:487 [ info nextcloud.sync.statustracker C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\syncfilestatustracker.cpp:239 ]:	Investigating "<some relative path>" OCC::SyncFileItem::NoStatus CSyncEnums::CSYNC_INSTRUCTION_UPDATE_METADATA OCC::SyncFileItem::Down
2024-08-31 23:43:39:487 [ info nextcloud.sync.statustracker C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\syncfilestatustracker.cpp:239 ]:	Investigating "<some relative path>" OCC::SyncFileItem::NoStatus CSyncEnums::CSYNC_INSTRUCTION_UPDATE_METADATA OCC::SyncFileItem::Down
2024-08-31 23:43:39:487 [ info nextcloud.sync.statustracker C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\syncfilestatustracker.cpp:239 ]:	Investigating "<some relative path>" OCC::SyncFileItem::NoStatus CSyncEnums::CSYNC_INSTRUCTION_SYNC OCC::SyncFileItem::Up
2024-08-31 23:43:39:487 [ debug nextcloud.gui.socketapi C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\socketapi\socketapi.cpp:228 ]	[ OCC::SocketListener::sendMessage ]:	Sending SocketAPI message --> "STATUS:SYNC:K:\\syncdir\\somepath" to QLocalSocket(0x1c91e8fc600)
2024-08-31 23:43:39:487 [ debug nextcloud.gui.socketapi C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\socketapi\socketapi.cpp:228 ]	[ OCC::SocketListener::sendMessage ]:	Sending SocketAPI message --> "STATUS:SYNC:K:\\syncdir" to QLocalSocket(0x1c91e8fc600)
2024-08-31 23:43:39:487 [ debug nextcloud.gui.socketapi C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\socketapi\socketapi.cpp:228 ]	[ OCC::SocketListener::sendMessage ]:	Sending SocketAPI message --> "STATUS:IGNORE:K:\\syncdir\\.nextcloudsync.log" to QLocalSocket(0x1c91e8fc600)
2024-08-31 23:43:39:487 [ debug nextcloud.gui.socketapi C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\socketapi\socketapi.cpp:228 ]	[ OCC::SocketListener::sendMessage ]:	Sending SocketAPI message --> "STATUS:IGNORE:K:\\syncdir\\.sync_34c5cd5d175d.db" to QLocalSocket(0x1c91e8fc600)
2024-08-31 23:43:39:487 [ debug nextcloud.gui.socketapi C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\socketapi\socketapi.cpp:228 ]	[ OCC::SocketListener::sendMessage ]:	Sending SocketAPI message --> "STATUS:IGNORE:K:\\syncdir\\.sync_34c5cd5d175d.db-journal" to QLocalSocket(0x1c91e8fc600)
2024-08-31 23:43:39:487 [ info nextcloud.sync.engine C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\syncengine.cpp:840 ]:	#### Reconcile (aboutToPropagate OK) ####################################################  936 ms
2024-08-31 23:43:39:487 [ debug nextcloud.sync.database C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\common\syncjournaldb.cpp:2799 ]	[ OCC::SyncJournalDb::commitInternal ]:	Transaction commit "post treewalk" and starting new transaction
2024-08-31 23:43:39:487 [ debug nextcloud.sync.database C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\common\syncjournaldb.cpp:2799 ]	[ OCC::SyncJournalDb::commitInternal ]:	Transaction commit "post stale entry removal" and starting new transaction
2024-08-31 23:43:39:487 [ debug nextcloud.gui.socketapi C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\socketapi\socketapi.cpp:228 ]	[ OCC::SocketListener::sendMessage ]:	Sending SocketAPI message --> "STATUS:SYNC:K:\\syncdir" to QLocalSocket(0x1c91e8fc600)
2024-08-31 23:43:39:487 [ info nextcloud.sync.engine C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\syncengine.cpp:894 ]:	#### Post-Reconcile end ####################################################  936 ms
2024-08-31 23:43:39:488 [ info nextcloud.gui.folder C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\folder.cpp:1182 ]:	#### Propagation start ####################################################
2024-08-31 23:43:39:488 [ debug nextcloud.gui.socketapi C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\socketapi\socketapi.cpp:515 ]	[ OCC::SocketApi::slotUpdateFolderView ]:	Not sending UPDATE_VIEW for "2" because status() is OCC::SyncResult::SyncRunning
2024-08-31 23:43:39:489 [ info nextcloud.gui.application C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\gui\owncloudgui.cpp:246 ]:	Sync state changed for folder  "https://server1_url/remote.php/dav/files/user2/" :  "Sync running"
2024-08-31 23:43:39:490 [ info nextcloud.sync.propagator.root.directory C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\owncloudpropagator.cpp:1582 ]:	scheduleSelfOrChild OCC::PropagatorJob::NotYetStarted pending uploads 0 subjobs state OCC::PropagatorJob::NotYetStarted
2024-08-31 23:43:39:490 [ warning nextcloud.sync.propagator.directory C:\Users\User\AppData\Local\Temp\windows-25183\client-building\desktop\src\libsync\owncloudpropagator.cpp:1261 ]:	Useless task found for file "<some newer relative file path>" instruction CSyncEnums::CSYNC_INSTRUCTION_SYNC

And it stops there. I'm not posting the whole thing (there's a lot of file names in it) but there is no error anywhere in the full log. Whatever kills the process do so without anything in the log.

Aug 31 '24 21:08 CleyFaye

Installed version 3.14 rc1 same problem starts and after 30 seconds application closes. I have data on a 128gb microsd on my surfage go2

Aug 31 '24 21:08 tigernero79