Mixxx crash upon RDP connection

[mixxxbot]

Reported by: dispatch00
Date: 2020-09-03T01:35:09Z
Status: New
Importance: Critical
Launchpad Issue: lp1894020
Tags: crash, windows
Attachments: mixxxbacktrace.txt

---

Mixxx crashes when I connect via remote desktop (RDP) to the Windows 10 Pro PC running it. Happens on 2.2.4 32-bit, 2.2.4 64-bit, and 2.3.0 64bit.

Windows 10 Pro 2004
AMD Ryzen 3200G
Built-in AMD Radeon Vega 8 (latest driver)
16GB RAM

Steps to reproduce:

1. Start Mixxx on PC from RDP session

2. Close RDP session

3. Reconect rdp session, Mixxx crashes immediately.

   Event viewer logs below; I have also created a backtrace which I will attach.

   Faulting application name: mixxx.exe, version: 2.3.0.7443, time stamp: 0x5ee15343
   Faulting module name: atio6axx.dll, version: 27.20.12027.1001, time stamp: 0x5f469dea
   Exception code: 0xc0000005
   Fault offset: 0x000000000172d81e
   Faulting process id: 0x2028
   Faulting application start time: 0x01d6818c3c425faf
   Faulting application path: C:\Program Files\Mixxx\mixxx.exe
   Faulting module path: C:\Windows\System32\DriverStore\FileRepository\u0358376.inf_amd64_1aefb33b1784bbc2\B358374\atio6axx.dll
   Report Id: 1a4a841e-5fa7-4e5e-9f07-b39730514332
   Faulting package full name:
   Faulting package-relative application ID:

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

Problem signature:
P1: mixxx.exe
P2: 2.3.0.7443
P3: 5ee15343
P4: atio6axx.dll
P5: 27.20.12027.1001
P6: 5f469dea
P7: c0000005
P8: 000000000172d81e
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CA6.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9DC0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9DD1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9DCF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9DEF.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mixxx.exe_b2784d371c4d363325108b769361fd547dc3a659_d4c05104_2e3b3cb5-c322-432b-86d4-e385bf338171

Analysis symbol:
Rechecking for solution: 0
Report Id: 1a4a841e-5fa7-4e5e-9f07-b39730514332
Report Status: 268435456
Hashed bucket: de11c34ada3270dbc05623784fc10e9c
Cab Guid: 0

[mixxxbot]

Commented by: dispatch00
Date: 2020-09-03T01:35:09Z
Attachments: mixxxbacktrace.txt

[mixxxbot]

Commented by: daschuer
Date: 2020-09-03T05:41:51Z

---

The atio6axx.dll is the AMD OpenGL driver. So I assume the crash is related to the waveforms and spinies in Mixxx.

To verify this you may start Mixxx with the --saveMode parameter to disable all OpenGl rendering.

Maybe you also find a waveform setting that does not crash.

Is the latest graphics driver installed. Maybe it is a known bug in the driver already fixed.

You may also try to downgrade the driver to check if it isn't a recently introduced issue.

[mixxxbot]

Commented by: daschuer
Date: 2020-09-03T05:45:46Z

---

00007FF690131007 A0 mixxx.WSpinny::render+597

The backtrack reveals that the spinny is causing the crash. So maybe it is sufficient to hide the spinies before remitting into the machine.

Does the crash also happen if you start Mixxx locally and remote into the machine with an already running Mixxx?

[mixxxbot]

Commented by: dispatch00
Date: 2020-09-03T16:26:36Z

---

Appreciate the quick responses!

Regarding graphics driver: I have tried older AMD graphics drivers as well as default generic MSFT driver. Mixxx crashes using all of them.

Regarding OpenGL: surely you are correct. I also experienced crashes after RDP disconnection which I was able to fix by disabling the waveforms. I did not think about the spinnies!

Regarding spinnies: You are correct, disabling spinnys allow me to start Mixxx from RDP session and subsequently connect at will and Mixxx does not crash.

Regarding local session vs RDP: if I start Mixxx from console session and subsequently connect via RDP, Mixx does not crash!

Again I appreciate your quick assistance and advice on this matter.  I now have two acceptable workarounds for this issue (start from console and/or disable spinnies/waveforms); I will attempt to experiment with --saveMode parameter and report back.