New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 10 Client 3.2.1 keep crashing #3243
Comments
same for me, only if enable virtual file OS: Windows 10 20H2 tried reinstall client but no success |
I can see the known problem of 3.2.0 in your logs. It was fixed in 3.2.1. However, it seems that the running app's version is still 3.2.0 according to your logs. Could you try the following:
With the steps above, you'll make sure you're running the latest 3.2.1 release. Also, you'll make sure the broken state of 3.2.0 is not affecting the latest 3.2.1 installation. @mgallien ping |
Same could be true for your case. If you've been running the Nextcloud release 3.2.0 before 3.2.1, the local state might have been broken and is still affecting 3.2.1 making the 3.2.0 issue to happen. I suggest you try the steps from my previous comment and let me know how it goes. |
@allexzander I have tried removing the app data folder as well as doing a complete reinstall and Nextcloud still becomes not responding after starting it up for the second time. Here is the log:
When it stops responding, it will also prevent me from opening another instance of explorer window. Force closing it via task manager will open explorer windows based on the amount of times I tried to open. Removing the explorer shell extensions resolved this, but the client still hangs regardless and constantly uses 5-15% of my cpu. The message shown on the desktop client when you hover over is These issues only occurs when I have VFS enabled. It's also not an issue with server side as I have another desktop that works flawlessly with it enabled. There are also instances where I would be unable to force close it in task manager, with a message along the lines of no access. |
I have completely reinstall nextcloud as your follows and rebooted my computer. It crashes again after connected to server. (Reusing previous local file directory) I have ensured that the client version is 3.2.1 It crashes too if I click the button below: Log from windows event viewer: (translated)
AppCrash_nextcloud.exe_a44096ba9a82603292d47fc9bd811247fb552f_88d53db4_bc759f81-5df1-4e7b-83ab-36fb72ff4a79.zip |
I ve clean uninstalled Nextcloud app with RevoUninstaller, removed any related folder, registry, ecc.. installed 3.2.1 but no success |
same issue, it appears to happen to happen when there is a large "difference" in files to be synced. |
For me 3.2.1 had straaange symptom. I made update, then just go out, and after i came back (hour or so) laptop had fans turned on (usually it is quiet). What i observed (in taskmanager) was - Nextcloud eat 30-35% of CPU power doing nothing (files were synced already, and computer wasn't used). When i try to turn it off using right click on Nextcloud icon on system tray, cpu was still used, and there still was Nextcloud.exe process eating CPU. I didn't have time to play with this, because i like silent laptop :) |
@sgtpepperaut That's what I thought too as I'm using Google FS and Cryptomator but I've already uninstalled them to check and it still doesn't work. Does explorer.exe still work for you when you have the client open? Mines won't open any new explorer windows unless I force quit the client. Disabling the .dll files loaded by Nextcloud to explorer prevents this from happening but client still has the cpu issue regardless. |
@weiw11 @sgtpepperaut @Archangel001 @kenvix While I am looking into this issue, it would be great if one of you could also try running a clean VM (possibly of the same Windows build that you are running physically) and install the Nextcloud 3.2.1 client in the VM. Then, you'd try to sync to your server from there. I am wondering if it is indeed a conflict with some other cloud-sync software. This may require some effort from you, so, I am not insisting, but, that would be nice to check that too. Asking this, as, at the moment I wasn't able to reproduce the issue on my physical and VM OS. I am gonna study logs today. I don't see any errors in the logs. Weird. BTW, looks like each of you people is having a different issue merged into one. |
@nicrame Do you remember if the VFS mode was turned on during that time, by any chance? |
I didn't use VFS. Last night 3.1.3 crashed few times, so i did back to version 3.0.1 and now it is stable and quiet. |
I am facing the same behaviour with 3.2.1 since I reactivated Onedrive, which makes me think it could be a conflict with other cloud-sync software, as you suggested. Unfortunately, I have no possibility of using any log right now as I am just moving, but I will ASAP. |
@allexzander I haven't been able to get my VM to work with windows but I have tested it on another machine with the same Windows build and it works fine. I'm not sure if it'll help but the image below lists the modules associated with explorer.exe which is freezing for me when nextcloud freezes. My other machine also has RTSS, WinSCP, and Nextcloud as well but not too sure about the system32 dlls though. |
Same Problem here, i tried to use sereral Nextcloud Versions, but no Luck so far. `Quelle Zusammenfassung Datum Status Beschreibung Problemsignatur Weitere Informationen über das Problem |
Was it always like that with 3.0.3? Or, did this start to happen after trying 3.2.1? |
It startet after the first Update to 3.2.1! |
@funky123 A workaround is to rename the folder |
@allexzander thanks alot! i will try this after my System is backed up (currently running) I have serveral files modified while the sync client is/was offline. i think
is that best way to save re-syncing time or do i miss someting? |
Has anyone attempted to use junctions (
|
Same issue Windows 10 Pro 20H2 client 3.2.2 seems to happen when having virtual file support |
I have the same problem with 3.2.2 in windows 10. It crashes almost immediately. I deleted the folder in appdata and I emptied the sync folder so there wouldn't be anything for it to do. |
Look at the issue I referenced. It's because of the sync exclude file in your nextcloud folder. |
I deleted that file and ran it again with no other changes and it runs until I add something to the sync folder. |
You have to make sure to select that file to always be downloaded. Otherwise it'll freeze. I just ended up moving it outside of my folder until the patch comes out. |
That file isn't in my syncing folder. It's in appdata\roaming\nextcloud |
The freeze is caused by the file in the syncing folder. Do a search for the file on syncing folder and delete/move any found. Or just right click and set them to be always downloaded. |
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
@weiw11 Is the issue still present in 3.2.4? The .sync-exclude file is now always downloaded with no way to make it virtual. This should fix the problem. |
No, it's not present as the crash was due to the sync file. |
The client 3.2.4 (and previous) is very unstable freezing a lot of times when using and clicking in the GUI. Sync is not working reliably. Issues when trying to open files directly. This thing is not usable. Will there be a big bug fix release? |
Expected behaviour
Sync my files normally
Actual behaviour
It crashes after connected to server
Steps to reproduce
Client configuration
Client version: 3.2.1
Operating system: Windows 10 20H2
OS language: zh_CN
Qt version used by client package (Linux only, see also Settings dialog):
Client package (From Nextcloud or distro) (Linux only):
Installation path of client: C:\Program Files\Nextcloud
Server configuration
Nextcloud version: latest docker fpm version (image was pulled yesterday)
Storage backend (external storage): default
Logs
I even had to disconnect my network to enable logging :(
log.zip
Messages from windows event viewer
The text was updated successfully, but these errors were encountered: