VirtualBox

Opened 8 years ago

Last modified 8 years ago

#15942 new defect

vm crash on macos upon cmd+c

Reported by: Richlv Owned by:
Component: other Version: VirtualBox 5.0.26
Keywords: Cc:
Guest type: Linux Host type: Mac OS X

Description

virtualbox 5.0.26 on macos. sometimes, the vm crashes (maybe once every two months or so). last time it specifically happened when (accidentally) pressing cmd+c.

the vm log ends like this :

92:22:28.521238 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:22:28.521254 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
92:22:28.521277 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:22:28.521337 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:22:28.521342 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:22:28.521346 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
92:22:28.521470 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885280 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885336 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x5
92:53:54.885344 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x5
92:53:54.885369 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:53:54.885369 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:53:54.885369 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:53:54.885369 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Using fallback buffer since no source bitmap is provided
92:53:54.885610 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:53:54.885626 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001251ee000 w=1440 h=900 bpp=32 cbLine=0x1680 flags=0x1
92:53:54.885656 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1440x900, Sending to async-handler
92:53:54.886947 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1440x900
92:53:54.886955 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1440x900
92:53:54.886959 GUI: UIFrameBufferPrivate::performResize: Size=1440x900, Directly using source bitmap content
92:56:51.703893 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
92:56:51.703989 VBVA: InfoScreen: [0] @0,0 1440x900, line 0x1680, BPP 32, flags 0x1
93:43:17.399764 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received
93:43:17.401758 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowWillExitFullScreenNotification' notification to corresponding machine-window...
93:43:17.401775 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowWillExitFullScreenNotification' received.
93:43:17.401778 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode about to exit, notifying listener...
93:43:17.441045 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenWillExit: Machine-window #0 will exit native fullscreen
93:43:17.968714 GUI: UIMachineWindow::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received
93:43:17.968735 UIMachineWindow::handleNativeNotification: Redirecting 'NSWindowDidExitFullScreenNotification' notification to corresponding machine-window...
93:43:17.968740 UIMachineWindowFullscreen::handleNativeNotification: Notification 'NSWindowDidExitFullScreenNotification' received.
93:43:17.968743 UIMachineWindowFullscreen::handleNativeNotification: Native fullscreen mode exited, notifying listener...
93:43:17.970210 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenDidExit: Machine-window #0 exited native fullscreen, changing visual-state to requested...

Change History (1)

comment:1 by Richlv, 8 years ago

spotted in dmesg of the host (although this might be unrelated) :

process VirtualBoxVM[19973] caught causing excessive wakeups. Observed wakeups rate (per sec): 315; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 13076558
aio_queue_async_request(): too many in flight for proc: 16.
aio_queue_async_request(): too many in flight for proc: 16.
aio_queue_async_request(): too many in flight for proc: 16.
VBoxDrv: host_vmxoff -> vmx_use_count=0
VirtualBox[52991] triggered unnest of range 0x7fff9ca00000->0x7fff9cc00000 of DYLD shared region in VM map 0xa9e914bb2cda7a9. While not abnormal for debuggers, this increases system memory footprint until the target exits.
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use