nextcloud / desktop

💻 Desktop sync client for Nextcloud
https://nextcloud.com/install/#install-clients
GNU General Public License v2.0
3.03k stars 797 forks source link

[Bug]: 3.13.0 on Windows 11 causes Explorer, desktop client to hang #6749

Open gellenburg opened 5 months ago

gellenburg commented 5 months ago

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

Bug description

Installed 3.13.0 on Windows 11 and after starting to sync the client now freezes and when it does it causes Explorer to freeze as well.

When it does, Task Manager reports that the client is still utilizing about 10% of CPU resources.

The only way to get Explorer to respond is to End Task the Nextcloud desktop client.

Steps to reproduce

  1. Install 3.13.0
  2. Begin syncing
  3. Both Explorer and the client will eventually hang

Expected behavior

I would expect that neither Explorer or the desktop client to hang.

Which files are affected by this bug

It's actually impossible to tell because I can't open up either the client or Explorer when it happens.

Operating system

Windows

Which version of the operating system you are running.

23H2 / 22635.3575

Package

Other

Nextcloud Server version

27.1.7

Nextcloud Desktop Client version

3.13.0

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?

Nextcloud Server logs

I don't have access to the server logs as I'm using Hetzner Storage Share.

Additional info

I can't even get to the "Create Debug Archive" because the application is frozen and unresponsive.

berbigou commented 5 months ago

W10 22H2 / NC-client 3.13.0 / NC-server 29.0.0 / no encryption NC-client crashes (no message, just stops) when trying to sync folder. already have tried that:

docker exec -it --user www-data nextcloud php occ files:scan --all
docker exec -it --user www-data nextcloud php occ files:cleanup
docker exec -it --user www-data nextcloud php occ maintenance:mode --on
docker exec -it --user root nextcloud-mariadb mysql -u root -p'<DatabaseRootPassword>' -D nextcloud -e 'delete from oc_file_locks where 1'
docker exec -it --user www-data nextcloud php occ maintenance:mode --off

only fix is downgrade client to 3.12.3, then everything is fine !

I also synchronize the same folders on the same computer under Linux, no pb with up-to-date client...

xelayz commented 5 months ago

W10 22H2 / NC-client 3.13.0 / NC-server 29.0.0 / no encryption NC-client crashes (no message, just stops) when trying to sync folder.

I have the same error. 3.13.0 is not working on W11 (23H2). I also downgraded to 3.12.3 and everything is working fine again.

BenjenJones commented 5 months ago

Same problem here. Client just crashes after sync started:

Edition Windows 11 Home Version 23H2 Installed at ‎14.‎12.‎2022 Operating system build 22631.3527 Performance Windows Feature Experience Pack 1000.22700.1003.0

3.12.3 works like a charm

Valentix53 commented 5 months ago

Same problem here. Client not responding even after killing and restarting the process. Also tried to kill explorer.exe to see if it was some kind on incompatibility but nothing... The linux client on my home pc works like a charm. I'm now trying downgrading: -3.12.5 does indeed not crash but also it doesn't sync -3.12.4 crashes really badly

If this helps my server is self hosted on a raspberry pi with dietPi.

Windows 11 Home 23H2 Installed at 25/‎01/‎2024 OS build 22631.3447 Windows Feature Experience Pack 1000.22688.1000.0 AMD Ryzen 7 5700U

Castiontone commented 5 months ago

As 3.12.3 seems to be the last stable version, related to #6721 ?

gellenburg commented 5 months ago

As 3.12.3 seems to be the last stable version, related to #6721 ?

Interesting. It definitely appears to be related to VFS. If I disable VFS I can sync now.

BenjenJones commented 5 months ago

As 3.12.3 seems to be the last stable version, related to #6721 ?

Interesting. It definitely appears to be related to VFS. If I disable VFS I can sync now.

Vfs = virtual files?

xelayz commented 5 months ago

As 3.12.3 seems to be the last stable version, related to #6721 ?

Interesting. It definitely appears to be related to VFS. If I disable VFS I can sync now.

I do not use the virtual file system. So its not only related to VFS.

farvardin commented 5 months ago

I had a similar problem with client 3.13 on linux (mint 21.3). I've upgraded my server to 28, it was the same: when starting nextcloud client, it will scan for files, then after it started to sync, it got stuck at 0% or 3%, then the UI was not responding. The CPU is at 100% and will eventually lead to the whole desktop being unresponsive (I had to reboot).

I've tried both the client from the distribution, and the 3.13 appimage, it was the same. I've also tried to disable bandwidth limit with no better behavior.

It started to act normally again when I've been back to the older 3.9.0 appimage.

JackV2020 commented 4 months ago

I think we with the Linux Desktop version have the same issue : https://github.com/nextcloud/desktop/issues/6711

BenjenJones commented 4 months ago

did something change with the 3.13.1? I don't dare to update and try out :)

JackV2020 commented 3 months ago

I know this is about Windows but I have the same issue on Linux. Just tried the AppImage 3.13.1 on my Ubuntu and saw memory fill up within some seconds until my desktop froze. Had to pull the plug and reboot and delete the AppImage asap and reboot again to get back up and running. Went back to AppImage version 3.12.5.

berbigou commented 3 months ago

W10 22H2 / NC-client 3.13.2 / NC-server 29.0.3 / no encryption NC-client doesn't crash anymore (in fact, it crashed once, I reinstalled 3.12.3, then 3.13.2) OK for now... Thanks

JackV2020 commented 3 months ago

Tried AppImage 3.13.2 on Ubuntu and had to kill it again and am back to 3.12.5 like before.

xelayz commented 3 months ago

did something change with the 3.13.1? I don't dare to update and try out :)

I tried with 3.13.2 on a fresh Windows installation and it is still not working. But now it crash instead of freezing. Why is it not fixed by the Nextcloud team? I mean its not a small bug, its a full failure.

farvardin commented 3 months ago

did something change with the 3.13.1? I don't dare to update and try out :)

I tried with 3.13.2 on a fresh Windows installation and it is still not working. But now it crash instead of freezing. Why is it not fixed by the Nextcloud team? I mean its not a small bug, its a full failure.

@xelayz I am affected as well (on 2 computers), but suppose it doesn't affect everyone and it might be complicated to trace this problem...

camilasan commented 3 months ago

I tried with 3.13.2 on a fresh Windows installation and it is still not working. But now it crash instead of freezing. Why is it not fixed by the Nextcloud team? I mean its not a small bug, its a full failure.

We have not reproduced this.

xelayz commented 3 months ago

I checked the Nextcloud Logs, but there is no error I think. But I found one in the Windows logs which belongs to the crash:

- EventData (Application Error)

  AppName nextcloud.exe 
  AppVersion 3.13.2.55620 
  AppTimeStamp 668bde53 
  ModuleName ntdll.dll 
  ModuleVersion 10.0.22621.3733 
  ModuleTimeStamp 67ca8829 
  ExceptionCode c0000005 
  FaultingOffset 0000000000078360 
  ProcessId 0x3ea8 
  ProcessCreationTime 0x1dad773852aedcc 
  AppPath C:\Program Files\Nextcloud\nextcloud.exe 
  ModulePath C:\Windows\SYSTEM32\ntdll.dll 
  IntegratorReportId 315adbc8-f3ed-4075-bfcd-6fd204c7b5f9 
  PackageFullName  
  PackageRelativeAppId

- EventData 

  Bucket 2126509959303174601 
  BucketType 4 
  EventName APPCRASH 
  Response Nicht verfügbar 
  CabId 0 
  P1 nextcloud.exe 
  P2 3.13.2.55620 
  P3 668bde53 
  P4 ntdll.dll 
  P5 10.0.22621.3733 
  P6 67ca8829 
  P7 c0000005 
  P8 0000000000078360 
  P9  
  P10  
  AttachedFiles \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4cac0b03-071a-48e0-92b9-2ba7cbb213d0.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.daced636-f6a9-451c-970e-6af4e81dc73e.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.82dad5a6-1f08-49a3-bb1b-3a3eacbc5271.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2412634e-2e30-4494-90dd-60a6b863900c.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a0d48d07-cf0d-4e9f-afdc-c85b7b08fb9c.tmp.xml 
  StorePath \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_nextcloud.exe_29b578c1eee2c8b3e88913fa678199e82907d54_b13d8584_95fead20-5954-4d0a-b9bf-b4674afac0a6 
  AnalysisSymbol  
  Rechecking 0 
  ReportId a108dcf9-8825-4208-8a27-70c9aad9220b 
  ReportStatus 268435456 
  HashedBucket 97abfeac0a2bfb16bd82e18a8f9899c9 
  CabGuid 0 

I mean my Windows is fresh, but there is still a problem with the newest Nextcloud client. Maybe something is wrong with my Nextcloud Server and their files which leads to an incompatibility with the latest Nexcloud client version or the Nextcloud client is broken.

Edit: It looks like the latest Nextcloud client version has problems with one of my drivers. So it is now a different problem than what was mentioned here in the start post. Here you can find more details:

https://github.com/nextcloud/desktop/issues/2282

I will try it all out and report back.

Edit2: Ok, I updated my driver, but Nextcloud still crash. I go back to 3.12.3 again. Hope with 3.14 it will be no problem anymore. Or maybe with new driver.

camilasan commented 1 month ago

do you still have this issue with 3.14.1?

berbigou commented 1 month ago

On Linux (Arch, KDE), no problem with 3.14.1 On Windows (W10), I stick to 3.12.3 , neither 3.13 nor 3.14 works without crashing.

Valentix commented 3 weeks ago

Can confirm that now (3.14.1) everything is working correctly on Windows 11 Home 23H2

XPhilipp commented 3 weeks ago

Windows 10 (22H2) - 3.14.1 not works, return to 3.12.3 (

berbigou commented 2 weeks ago

W10 22H2 / NC-client 3.14.1 / NC-server Nextcloud Hub 9 / no encryption I gave a new try to 3.14.1, seems to run without crashing on Windows, no pb excepted the "White-on-White Theme"

berbigou commented 2 weeks ago

3.14.1 crashed. back to 3.12.3