Desktop Client 3.2.2 crashes when I try to access menu of sync folder

Syncro20VTurbo · June 22, 2021, 7:01am

Hi there,

unfortunately I have a strange problem with the desktop client version 3.2.2.
I have created two folders for syncronization, (pictures and music). The Pictures folder works fine and syncs. When clicking on the three dots next to it in the settings menu, I can select the appropriate options.
The music folder does not work the same way. When I click on the three dots there, the client closes without comment. Manually deleting the folder on the Nextcloud server does not change the behavior either. If I manually create the folder on the server, the client crashes without comment right after starting.

Video zum Problem

Can anyone help me with this?
If you have any questions, please feel free to ask.
As you may see, I’m not a native english speaker, so if German is easier for you, you can answer in german as well.

Best thanks and kind regards

Mathias

wwe · June 22, 2021, 7:15am

HI, the new client has some issue related to the settings menu e.g.:

github.com/nextcloud/desktop

[3.2.2] Clicking on the 3 dots button next to filesync status is really slow

opened 11:02PM - 15 Apr 21 UTC

eibex

0. Needs triage bug feature: :gear: settings os: :door: Windows

### How to use GitHub * Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue. * Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue. * Subscribe to receive notifications on status change and new comments. ### Expected behaviour When clicking the button (highlighted in red below) the menu comes up immediately ![image](https://user-images.githubusercontent.com/40539455/114947686-dea5a480-9e4d-11eb-841a-224ceeb19276.png) ### Actual behaviour The menu comes up after 5 seconds or more, making you wonder if you actually pressed the button or if it does anything. The CPU usage doesn't even spike that much (from 2% to 10% at most). ### Steps to reproduce 1. Click the button highlighted in the picture above ### Client configuration Client version: 3.2.0  Operating system: Win10 OS language: English Installation path of client: Default ### Logs ``` [...] 2021-04-16 00:58:27:863 [ warning nextcloud.sync.vfs.cfapi ]: Couldn't find pin state for regular non-placeholder file "C:\\Users\\***USERNAME***\\Nextcloud\\Folder1\\Folder2\\file1.ext" 2021-04-16 00:58:27:863 [ warning nextcloud.sync.vfs.cfapi ]: Couldn't find pin state for regular non-placeholder file "C:\\Users\\***USERNAME***\\Nextcloud\\Folder3\\Folder4\\file2.ext" 2021-04-16 00:58:27:863 [ warning nextcloud.sync.vfs.cfapi ]: Couldn't find pin state for regular non-placeholder file "C:\\Users\\***USERNAME***\\Nextcloud\\Folder5\\Folder6\\file3.ext" 2021-04-16 00:58:27:863 [ warning nextcloud.sync.vfs.cfapi ]: Couldn't find pin state for regular non-placeholder file "C:\\Users\\***USERNAME***\\Nextcloud\\Folder7\\Folder8\\file4.ext" [...] ``` There is a line for this for basically every file in the Nextcloud directory. I actually think this is the reason the button is slow: it's writing a lot of lines to the logfile. All those lines are generated whenever I press the button.

it looks the problem is related to excessive logging performed while entering “settings” menu.

Take a look if you find errors in windows eventlog - maybe you find known issue or you can file new one on github…

this looks exactly like your problem:

github.com/nextcloud/desktop

Windows 10 Client 3.2.1 keep crashing

opened 12:48PM - 30 Apr 21 UTC

kenvix

bug crash feature: :minidisc: virtual filesystem

### Expected behaviour Sync my files normally ### Actual behaviour It c…rashes after connected to server ### Steps to reproduce 1. Launch nextcloud desktop 2. Wait for it to connect with the server 3. It crashed. ### 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 :( 1. Client logfile: [log.zip](https://github.com/nextcloud/desktop/files/6405396/log.zip) Messages from windows event viewer ```xml - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2021-04-30T12:43:38.8203629Z" /> <EventRecordID>27557</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>EXCALIBUR</Computer> <Security /> </System> - <EventData> <Data>nextcloud.exe</Data> <Data>3.2.1.25340</Data> <Data>6089359f</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.19041.906</Data> <Data>2f2f77bf</Data> <Data>c0000005</Data> <Data>000000000002ae08</Data> <Data>2598</Data> <Data>01d73dbdd64e5bfd</Data> <Data>C:\Program Files\Nextcloud\nextcloud.exe</Data> <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data>608bae21-ce02-460d-842e-e71b2d6d6bcc</Data> <Data /> <Data /> </EventData> </Event> ```

error should appear in eventlog:

Faulting application name: nextcloud.exe, version: 3.2.1.25340, time stamp: 0x6089359f
Faulting module name: KERNELBASE.dll, version: 10.0.19041.906, time stamp: 0x2f2f77bf
Exception code: 0xc0000005
Error offset: 0x000000000002ae08
Error process ID: 0x4598
Error application startup time: 0x01d73e1acbf34b93
Error application path: C:\Program Files\Nextcloud\nextcloud.exe
Error module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 7428e2d3-80fb-43d9-9198-5564b9d314e8
Full name of the error package:
The relative application ID of the error package:

Solution might be to completely remove the client and local state and re-install 3.2.1 from scratch

Syncro20VTurbo · June 22, 2021, 8:14am

Well, thanks so far.

I looked at the Windows eventlog and provoked the crash of Nextcloud.

Name der fehlerhaften Anwendung: nextcloud.exe, Version: 3.2.2.25439, Zeitstempel: 0x60af933e
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.19041.1023, Zeitstempel: 0x924f9cdb
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000002ae38
ID des fehlerhaften Prozesses: 0x658
Startzeit der fehlerhaften Anwendung: 0x01d76734a5d9a31b
Pfad der fehlerhaften Anwendung: C:\Program Files\Nextcloud\nextcloud.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: e1e797ca-18e3-4720-a24e-8dae041930a0
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

A second later, some more information about the crash is written:

Fehlerbucket 1512339385787856191, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: nextcloud.exe
P2: 3.2.2.25439
P3: 60af933e
P4: KERNELBASE.dll
P5: 10.0.19041.1023
P6: 924f9cdb
P7: c0000005
P8: 000000000002ae38
P9: 
P10: 

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6332.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER645B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER646C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER647A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER64AA.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_nextcloud.exe_95266e718d85828e2d693b923619cefbd473f685_e05769ad_9ab65a9f-31e1-4990-87ce-adba68e50d0f

Analysesymbol: 
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: e1e797ca-18e3-4720-a24e-8dae041930a0
Berichtstatus: 268435456
Bucket mit Hash: e41026004acabf9db4fce8a89db7b53f
CAB-Datei-Guid: 0

I’m not sure what to do with this now, or if it has anything to do with the three dots problem.
De- and reinstalled already for several times. Just not a solution.

The three dots Problem is fixed in my case when I turned of the QNAP NAS synchronisation app which syncs the same folders as the nextcloud.
Unfortunately the app crashes instantly after setting up the musik sync pair again.
I keep trying.

Maybe just another thing:
When I manually delete the folder on the nextcloud server, the app doesn’t crash again until I click on the three dots.
I don’t have any idea…

Syncro20VTurbo · July 9, 2021, 7:14pm

So, to bring this to a close:
I have now sit down again intensively and tried everything possible through. In the end, the only thing that helped was uninstalling Nextcloud, removing all Nextcloud entries in the registry and manually deleting the folders in the browser.
Real shit, but after the reinstallation it works now at least. The client doesn’t seem to be bug-free…