[Bug]: Client 3.14.0/3.14.1 crash in RDP session.

[sjmoller]

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

When I RDP to the Win10 client, the Nextcloud client crashes. If I login directly on the client, the Nextcloud client starts normally. I made sure my VC++ 2015-2022 x64/x86 is up2date (vm3dgl64.dll). This is a fresh install of the 3.14.1 client. nextcloud-3.13.4 works.

Found i EventLog-Application:

Faulting application name: nextcloud.exe, version: 3.14.1.55839, time stamp: 0x66f6776f Faulting module name: vm3dgl64.dll, version: 3.6.0.0, time stamp: 0x66a16726 Exception code: 0xc0000005 Fault offset: 0x0000000000e3696d Faulting process id: 0x2958 Faulting application start time: 0x01db130d5d0e75e5 Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe Faulting module path: C:\WINDOWS\SYSTEM32\vm3dgl64.dll Report Id: f052a978-a246-491f-8359-7d03d963426f Faulting package full name: Faulting package-relative application ID:

Steps to reproduce

RDP to the client host.

Expected behavior

Nextcloud client 3.14.x crashes.

Which files are affected by this bug

nextcloud.exe

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Official Windows MSI

Nextcloud Server version

30.0.0

Nextcloud Desktop Client version

3.14.1

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 Disabled

Are you using an external user-backend?

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

Nextcloud Server logs

Not server related

Additional info

No response

[mgallien]

looks like a crash from the graphics API that is being used by the UI would be worth investigating if you can find a workaround following the steps there:

• debug logs: https://doc.qt.io/qt-6/qrhi.html#error-reporting
• select alternate rendering backend https://doc.qt.io/qt-6/qtquick-visualcanvas-scenegraph-renderer.html#rendering-via-the-qt-rendering-hardware-interface

[henkelm]

ID 1000

Name der fehlerhaften Anwendung: nextcloud.exe, Version: 3.14.1.55839, Zeitstempel: 0x66f6776f Name des fehlerhaften Moduls: vm3dgl64.dll, Version: 3.6.0.0, Zeitstempel: 0x66a16726 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000e3696d ID des fehlerhaften Prozesses: 0x1f2c Startzeit der fehlerhaften Anwendung: 0x01db205e2f966893 Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Nextcloud\nextcloud.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\vm3dgl64.dll Berichtskennung: 3dd044e5-618b-4345-afde-c92e66c77be9 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

[vkhacker]

Faulting application name: nextcloud.exe, version: 3.14.0.55826, time stamp: 0x66e54b9d Faulting module name: vm3dgl64.dll, version: 3.6.0.0, time stamp: 0x66a16726 Exception code: 0xc0000005 Fault offset: 0x0000000000e3696d Faulting process id: 0x286c Faulting application start time: 0x01db221e469d3797 Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe Faulting module path: C:\WINDOWS\SYSTEM32\vm3dgl64.dll Report Id: 6d6b441f-da0d-400f-b738-2c5891528635 Faulting package full name: Faulting package-relative application ID:

Faulting application name: nextcloud.exe, version: 3.14.1.55839, time stamp: 0x66f6776f Faulting module name: vm3dgl64.dll, version: 3.6.0.0, time stamp: 0x66a16726 Exception code: 0xc0000005 Fault offset: 0x0000000000e3696d Faulting process id: 0x286c Faulting application start time: 0x01db221d123e8d99 Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe Faulting module path: C:\WINDOWS\SYSTEM32\vm3dgl64.dll Report Id: f675fa4e-7dcb-4eff-85f5-cb2ba58d81dc Faulting package full name: Faulting package-relative application ID:

Faulting application name: nextcloud.exe, version: 3.14.2.55930, time stamp: 0x67129506 Faulting module name: vm3dgl64.dll, version: 3.6.0.0, time stamp: 0x66a16726 Exception code: 0xc0000005 Fault offset: 0x0000000000e3696d Faulting process id: 0x3050 Faulting application start time: 0x01db23a2ccb26c92 Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe Faulting module path: C:\WINDOWS\SYSTEM32\vm3dgl64.dll Report Id: 20aae38b-6a5d-40b5-b238-f25fb004b6b9 Faulting package full name: Faulting package-relative application ID:

[budzi-2bi]

Here is another one, this one is running on Windows 10 VM (VMware Workstation Pro 17.6.1 build-24319023):

Faulting application name: nextcloud.exe, version: 3.14.3.55943, time stamp: 0x67238c6c
Faulting module name: vm3dgl64.dll, version: 3.6.0.0, time stamp: 0x66a16726
Exception code: 0xc0000005
Fault offset: 0x0000000000e3696d
Faulting process id: 0x2f44
Faulting application start time: 0x01db2fca6b177216
Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe
Faulting module path: C:\WINDOWS\SYSTEM32\vm3dgl64.dll
Report Id: 2ed79ae3-ce77-4d9a-bc32-8eb5051580ab
Faulting package full name: 
Faulting package-relative application ID: 

I've set the QSG_INFO=1 environment variable and then started and got this:

Fault bucket 1715399472271708049, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: nextcloud.exe
P2: 3.14.3.55943
P3: 67238c6c
P4: vm3dgl64.dll
P5: 3.6.0.0
P6: 66a16726
P7: c0000005
P8: 0000000000e3696d
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF313.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF381.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF3A1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF39F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF3B0.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_nextcloud.exe_c44a7b3826fcd8b0197f6762695e13dfc98a354_827aaf23_408d6d55-3da1-4ca0-989c-39a266419ea6

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2e47b754-a178-4fd9-81ce-e83c7470bdd0
Report Status: 268435456
Hashed bucket: ad94002c8eba6f69b7ce52bb40a5cf91
Cab Guid: 0

The mentioned WER file is attached. Hope this helps.Report.wer.txt

I reverted back to version 3.13.3 and it works on this VM.

On the host (also Windows 10) v3.14.4 works without problems, so far.

[Kontergewicht]

Same error on 3.15.2:

Name der fehlerhaften Anwendung: nextcloud.exe, Version: 3.15.2.56128, Zeitstempel: 0x67604cd9
Name des fehlerhaften Moduls: vm3dgl64.dll, Version: 3.6.0.0, Zeitstempel: 0x66a16726
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000e3696d
ID des fehlerhaften Prozesses: 0x3450
Startzeit der fehlerhaften Anwendung: 0x01db5127d399b5d1
Pfad der fehlerhaften Anwendung: C:\Program Files\Nextcloud\nextcloud.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\vm3dgl64.dll
Berichtskennung: 59fd45f1-22d5-4fdc-a5de-2977f52fcaec

[vkhacker]

Nextcloud working after adding system environment SVGA_ALLOW_LLVMPIPE=0 (you need to re-login to the system or reboot the OS).

[sjmoller]

Nextcloud working after adding system environment SVGA_ALLOW_LLVMPIPE=0 (you need to re-login to the system or reboot the OS).

Confirmed.

[camilasan]

I am trying to fix it with #7687 need to consider RDP too, our initial idea was to try to check for VMware only.

[sjmoller]

I should probably mention that the Win10 client in this bug report is an VMware ESXi guest as well. The original bug report in this thread was focused on RDP sessions as this was the only scenario I experienced the crashes. When opening a VMware console connection (i.e. not RDP) the Nextcloud client did not crash, so I assumed the root cause was RDP somehow. It stands to reason that this bug is related to VMware only, and has nothing to do with RDP.

[Kontergewicht]

Confirmed, too. Thanks for the solution.

[Xerionty]

Having the same issue, fixed with the ENV variable change.

[camilasan]

Please try running https://github.com/nextcloud-releases/desktop/releases/download/v3.16.0-rc1/Nextcloud-3.16.0-rc1-x64.msi In this release we are trying to detect if you using RDP and set SVGA_ALLOW_LLVMPIPE to 0.

[Azgar1998]

Hello, I have the same issue with 3.15.3. While waiting for the fix with a stable version, I downgraded to version 3.13.4.

[camilasan]

Hello, I have the same issue with 3.15.3. While waiting for the fix with a stable version, I downgraded to version 3.13.4.

did the release candidate also crash?

[Azgar1998]

Hello,

Yes, I tried version 3.16.0 RC1, I have the same Issue

[camilasan]

Yes, I tried version 3.16.0 RC1, I have the same Issue

Then for now please use the workaround:

Nextcloud working after adding system environment SVGA_ALLOW_LLVMPIPE=0 (you need to re-login to the system or reboot the OS).

[Rello]

Hello,

can you please retest if this still exists in the current version? thank you