Mixxx freezes when unplugging monitor

[mixxxbot]

Reported by: tharrison1 Date: 2014-08-30T04:07:40Z Status: Triaged Importance: Critical Launchpad Issue: lp1363343 Attachments: [the mixxx log file](https://bugs.launchpad.net/bugs/1363343/+attachment/4190676/+files/the mixxx log file), [Debug Diagnostic Tool v2 dump](https://bugs.launchpad.net/bugs/1363343/+attachment/4190677/+files/Debug Diagnostic Tool v2 dump)

---

I am running: Mixxx 1.11.0 x64 on Windows 7 Home Premium x64 Intel i3 2.4ghz with 8gig ram System Audio: Realtek High Definition Audio HDMI Audio: Intel(R) Display Audio

Problem: Mixxx crashes when a hdmi monitor is removed while a deck is playing. This does not happen if there is no music playing. Note that the htmi audio port is never used, and is never selected as an output in mixxx. Also, under audio settings, I have Primary Sound Device selected as output, not the system specific device. This will not happen if I select a specific device as the output device.

Example: I have a HTMI monitor that has audio outputs on it(because it is htmi). When that gets connected or disconnected during the mixxx runtime, mixxx crashes. Same with my usb speekers, and usb sound card.

Additional: If I change any of the hardware while mixxx is not running, mixxx will warn me on the next run that there is no output device selected in the output tab, and sure enough, there are no aduio devices selected for any of the outputs or inputs(they are in the lists though).

Logs:

/* From Event Viewer -> Windows Logs -> Application */
Log Name:      Application
Source:        DbgHost
Date:          8/30/2014 12:03:07 AM
Event ID:      1
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Thomas-PC
Description:
The following process dump file was generated:
 C:\Program Files\DebugDiag\Logs\Crash rule for all instances of mixxx.exe\mixxx__PID__6348__Date__08_30_2014__Time_12_02_59AM__937__Second_Chance_Exception_C0000005.dmp
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DbgHost" />
    <EventID Qualifiers="0">1</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-08-30T04:03:07.000000000Z" />
    <EventRecordID>99565</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thomas-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>C:\Program Files\DebugDiag\Logs\Crash rule for all instances of mixxx.exe\mixxx__PID__6348__Date__08_30_2014__Time_12_02_59AM__937__Second_Chance_Exception_C0000005.dmp</Data>
  </EventData>
</Event>

[mixxxbot]

Commented by: tharrison1 Date: 2014-08-30T04:07:40Z Attachments: [the mixxx log file](https://bugs.launchpad.net/mixxx/+bug/1363343/+attachment/4190676/+files/the mixxx log file)

[mixxxbot]

Commented by: tharrison1 Date: 2014-08-30T04:09:49Z Attachments: [Debug Diagnostic Tool v2 dump](https://bugs.launchpad.net/mixxx/+bug/1363343/+attachment/4190677/+files/Debug Diagnostic Tool v2 dump)

[mixxxbot]

Commented by: ywwg Date: 2014-08-30T12:54:47Z

---

Yeah this is a well-known and hard problem to fix. For now all I can say is "don't do that."

[mixxxbot]

Commented by: rryan Date: 2014-09-15T21:09:24Z

---

Hm, I'm afraid this looks like a bug in ig4icd64.dll (your graphics driver):

ig4icd64!ShCompile ig4icd64!DllMain ig4icd64!DllMain ig4icd64!DllMain ig4icd64!DrvSwapBuffers OPENGL32!wglSwapBuffers GDI32!SwapBuffers QtOpenGL4!QGLContext::swapBuffers

Looks like you removed the monitor right in the middle of Mixxx issuing a command to the graphics driver. I can only guess that the driver didn't like that and crashed. :-/ can't think of anything in Mixxx that we could fix here.