-
Notifications
You must be signed in to change notification settings - Fork 20
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
Crashes when switching from dual-monitor to single-monitor #9
Comments
Definitely repeatable. Going between (to or from) single-multi-monitor setup (i.e. laptop dock with external monitor used as extension of desktop) crashes .Net framework and makes WinGrooveshark quit. |
I, too, get this issue. I have .NET dump info. See the end of this message for details on invoking ************** Exception Text ************** ************** Loaded Assemblies ************** CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dllSystem CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dllWinGrooves CodeBase: file:///C:/Users/benjamin.hayes/AppData/Local/Apps/2.0/G992MO2P.0HD/4515NNXA.OD1/wing..tion_3115f29dc0abc440_0001.0000_5719ada70b72d261/WinGrooves.exeSystem.Windows.Forms CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dllSystem.Drawing CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dllSystem.Configuration CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dllSystem.Xml CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dllMicrosoft.WindowsAPICodePack.Shell CodeBase: file:///C:/Users/benjamin.hayes/AppData/Local/Apps/2.0/G992MO2P.0HD/4515NNXA.OD1/wing..tion_3115f29dc0abc440_0001.0000_5719ada70b72d261/Microsoft.WindowsAPICodePack.Shell.DLLMicrosoft.WindowsAPICodePack CodeBase: file:///C:/Users/benjamin.hayes/AppData/Local/Apps/2.0/G992MO2P.0HD/4515NNXA.OD1/wing..tion_3115f29dc0abc440_0001.0000_5719ada70b72d261/Microsoft.WindowsAPICodePack.DLLWindowsBase CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dllPresentationCore CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dllPresentationFramework CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dllSystem.Xaml CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dllSystem.Core CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dllMicrosoft.mshtml CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dllAccessibility CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll************** JIT Debugging ************** For example: When JIT debugging is enabled, any unhandled exception |
I am on a desktop and I am unable to reproduce this error. Does it only happen when you guys go from single monitor to dual monitor with a laptop dock. Is anyone able to produce this with a desktop. I am running Windows 8. |
So - I haven't figured out the exact combination to make it happen, but it happens often.
It crashes (I think the .net framework) when I have WinGrooves open (not necessarily playing music) and I go from a dual-monitor setup to a single-monitor setup - possibly when/if I put it in sleep mode between it, but that doesn't seem to be a requirement.
I do this often because I use it on a laptop and when it is docked, I have 2 monitors. When I undock it, i.e. when I go home, it crashes, or crashes when I un-sleep my laptop.
Thought this would be a good bug report :-)
The text was updated successfully, but these errors were encountered: