[Bug]: Nextcloud Desktop crashes shortly after start in version 3.13.0

[claell]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

I know, one should maybe not update to the ...0 releases of Nextcloud Desktop.

Still, I took the risk. Now, the client closes itself/crashes after launching it.

Steps to reproduce

Unknown

Expected behavior

No crash

Which files are affected by this bug

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Other

Nextcloud Server version

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 Enabled

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

[schliesser]

Heyho,

my 3.13.0 Desktop client on Windows 11 (Version 10.0.22631 Build 22631) also crashes.

So far I've investigated the following behaviour:

• ✅ Pausing all syncs immediatly after start -> Client keeps running
• ✅ Enable Sync for a folder that has no changes -> Client keeps running
• ✅ Enable Sync for a folder that has only local updates on my Windows machine -> Syncs to NC Server correctly -> No crash
• ❌ Enable Sync for a folder that has updates on server side -> Client crashes on file write

Hope that helps.

Maybe related to #6566 ?

---

Edit: Downgraded client to 3.12.1 with winget -> everything works fine again

[Aesculapius]

I'm seeing the same behavior with 3.13.0. with the same results as far as pausing sync keeping the client running.
I inspected the local log files but there's nothing interesting in it; the last lines read

2024-06-11 22:38:54:894 [ info nextcloud.sync.statustracker C:\Users\User\AppData\Local\Temp\windows-22489\client-building\desktop\src\libsync\syncfilestatustracker.cpp:239 ]: Investigating "InstantUpload/Camera/2024/06/20240609_184323.jpg" OCC::SyncFileItem::NoStatus CSyncEnums::CSYNC_INSTRUCTION_NEW OCC::SyncFileItem::Down

Server-side, I'm seeing these lines at the end:

{"reqId":"g8mdSCV8TBQIyVoMtVna","level":0,"time":"2024-06-11T20:49:17+00:00","remoteAddr":"masked","user":"Laurens","app":"workflowengine","method":"PROPFIND","url":"/remote.php/dav/files/Laurens/InstantUpload/Camera/2024/05","message":"Flow activation: rules were requested for operation Block access to a file","userAgent":"Mozilla/5.0 (Windows) mirall/3.13.0stable-Win64 (build 20240423) (Nextcloud, windows-10.0.22631 ClientArchitecture: x86_64 OsArchitecture: x86_64)","version":"29.0.1.1","data":{"app":"workflowengine","level":"0"}}

{"reqId":"g8mdSCV8TBQIyVoMtVna","level":0,"time":"2024-06-11T20:49:18+00:00","remoteAddr":"masked","user":"Laurens","app":"workflowengine","method":"PROPFIND","url":"/remote.php/dav/files/Laurens/InstantUpload/Camera/2024/05","message":"No flow configurations is going to run Block access to a file","userAgent":"Mozilla/5.0 (Windows) mirall/3.13.0stable-Win64 (build 20240423) (Nextcloud, windows-10.0.22631
ClientArchitecture: x86_64 OsArchitecture: x86_64)","version":"29.0.1.1","data":{"app":"workflowengine","level":"0"}}

Finally, these are on the server configuration logging page:

Not sure if it relates...
I'm running NC 29.0.1 and will now try to update to latest 29.0.2

[Aesculapius]

The problem still persists in 29.0.2...
For now I've downgraded to 3.12.5 and the problem went away...

[mgscreativa]

Same here, had to downgrade to v3.4.2

[rosa2]

Same problem with Ubuntu 22.04.4.
It freezes with large folders. I have several servers. I have to stop sync for all and then, one by one re-enable the sync.
It gets very slow.
Is it a way to downgrade with not loosing all the configuration? Thanks

[mgscreativa]

I can't find any old packages in PPA archives!

[Phx01]

Also the same on Fedora 40 with Nextcloud client v3.13.0.

Downgrading to 3.12.1 generally works. However, even that version goes haywire if you start entirely unrelated applications, e.g. Steam client. Once Steam is started, the Nextcloud client (v3.12.1) can be started again and it behaves normal going forward. However, it can as well be reproduced 100% by simply quitting Steam and restarting it. I honestly do not know what is going on at the start of Steam, but it is likely the Nextcloud client is writing to memory it shouldn’t and then when the Steam client starts, it itself writes to that address making the Nextcloud client unstable.

While it is absolutely possible that the Steam client is doing something wrong, since only the Nextcloud client is affected and only during Steam startup, I tend to believe that it is likely caused by the Nextloud client, which with v3.13.0 expanded this pre-existing memory leak.

[janarzz]

Latest Nextcloud desktop still not work.
When i open it, then immediately crash.
I updated Nextcloud server to 29.0.3, but desktop still crash.

[Matth3wW]

Downgrading to 3.12.1 generally works. However, even that version goes haywire if you start entirely unrelated applications, e.g. Steam client.

I'm having this issue as well.

• Operating System: Fedora 40 (latest as of 2024-06-25)
  

• Nextcloud Client: 3.13.0
  

• Nextcloud Server: 29.0.2 selfhosted on a proxmox debian LXC running LAMP stack.
  

Downgrading to 3.12.1 fixes the issue. Upgrading back to 3.13.0 has the issue return.

However, on 3.12.1, I do not have the issue you have while launching steam.

[janarzz]

I hope next desktop update fix this issue.

[mgscreativa]

Using alpha 3.13.50 from alpha PPA hangs too https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client-alpha

[EddyXorb]

I confirm the issue for Windows 11 23H2 Build 22631.3737 and nextcloud client 3.13.0. Crashes after less than a minute after start, blocking the windows file explorer completely and making it impossible to open programs via right-click on the lower windows task list, which is very annoying.

[claell]

This seems to have gotten resolved for me after updating to 3.13.1. Possibly related to a host that isn't reachable anymore.

[janarzz]

This seems to have gotten resolved for me after updating to 3.13.1. Possibly related to a host that isn't reachable anymore.

Hi, i tryng to use latest version 3.13.1.
Still crashing! I downgraded my desktop back to 3.12.4 version

[steumac]

Hi, 3.13.0 and 3.13.1 Windows 11 still crashing. Server version 27.1.11. Downgraded to 3.12.3 and working good so far.

[frivascl]

I had the same problem. Just delete .sync* and ._sync* and worked again.