With dual monitor setup, VirtualBox Crashes when in seamless mode and try to a phsical monitor is removed. Win7-64 host, linux guest

[zzxt]

How to reproduct. On a windows 7 64bit host with two physical monitor. Setup a VM with two Vmonitors, boot up the VM and login, then ctrl+L to go into seamless mode, each Vmonitor will use one physical monitor. Then disconnect one physcial monitor (by unplugging the cable), windows 7 will detect its gone. Then try click on anywhere inside the VM Vmonitor, it will hang, then crash.

However, if it is not in seamless mode when removing the physical monitor, it won't crash.

I don't think the graphic cards matters, I had this issue on a few different machines with nvidia/intel graphics.

This is especially anonying on laptops conntected to an external monitor. When I put the laptop to sleep, and go somewhere and wake up again without the external monitor, the VBox would crash.

I'm programmer, so if there's any information needed, I'm glad to help.

[zzxt]

VBox crash log

[mcorley]

Really hate this bug and would love a fix. Love working in seamless and usually I can remember to switch modes as the workaround before sleeping or disconnecting my monitor but sometimes I forget and then lose the contents of the VM. Has happened a number of times.

[zzxt]

Hi Guys, this has been reported for two months now. I know everyone must be very busy. But will someone look at this problem? Or maybe an update on when this would be looked upon? Much appreciated, thank you very much.

[Prototyped`]

I've had the crash manifest on VirtualBox 4.3.28, Windows 7 x64 Enterprise host, Ubuntu 12.04 LTS guest, in a slightly different manner. The guest starts up fine and even runs OK for a few minutes. Then the screen flashes (as if the dwm or display driver were crashing and restarting) and I find some host (not guest) windows have moved screens. The next time I click in a seamless guest window the VM aborts.

I checked the Windows Event Log to find out if the screen flashes had anything to do with dwm or the display driver -- but there was nothing like that in the Event Log suggesting something else was causing the flashes.

I have four recent crash logs attached. There seems to be a pattern -- the last few lines of each include things like

00:15:22.172751 UIMachineLogic: Host-screen geometry changed.
00:15:22.341581 UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2560x1440
00:15:22.456731 UIMachineLogic: Host-screen available-area changed.
00:15:23.595239 UIMachineLogic: Host-screen geometry changed.
00:15:23.622540 UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2560x1440
00:15:24.633729 VMMDev::SetVideoModeHint: got a video mode hint (2560x1440x0)@(0x0),(1;0) at 0
00:15:24.637011 VBVA_INFO_SCREEN: [0] @0,0 2560x1440, line 0x2800, BPP 32, flags 0x1
00:15:24.637061 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000011660000 w=2560 h=1440 bpp=32 cbLine=0x2800, flags=0x1
00:15:24.637074 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=10240, Size=2560x1440, Sending to async-handler..
00:15:24.721191 UIMachineLogic: Host-screen available-area changed.
00:15:24.748674 UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 2560x1440

Might it have something to do with the guest notifications for new screen size?

[rje]

Having the same issue. Looks like a duplicate of: https://www.virtualbox.org/ticket/14409

[denfromufa]

I think this is similar issue:

https://www.virtualbox.org/ticket/12881

[kler]

I have a similar issue, and found a workaround.

In my case it's seems that it's not related to multiple displays, but to sound. My monitor is connected via displayport, and my monitor is also my default sound device.

Workaround is to disable sound in guest. I'm using my virtual environment for development, so in my case this is acceptable.

Settings -> Audio -> Uncheck: "Enable audio"

• VirtualBox version: Version 5.1.26 r117224 (Qt5.6.2)
• Host: macOS Sierra 10.12.6
• Guest: Ubuntu 16.04.3 LTS

[mgriff]

This actually resolved the issue for me 100%. Went back in and turned Audio back on and it crashed again.

Crashed Thread: 35 Dispatch queue: com.apple.audio.CADispatchQueue.SerialQueue

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [0]

Replying to kler:

I have a similar issue, and found a workaround.

In my case it's seems that it's not related to multiple displays, but to sound. My monitor is connected via displayport, and my monitor is also my default sound device.

Workaround is to disable sound in guest. I'm using my virtual environment for development, so in my case this is acceptable.

Settings -> Audio -> Uncheck: "Enable audio"

• VirtualBox version: Version 5.1.26 r117224 (Qt5.6.2)
• Host: macOS Sierra 10.12.6
• Guest: Ubuntu 16.04.3 LTS