Opened 6 years ago
Last modified 5 years ago
#18030 new defect
EXC_BAD_ACCESS (SIGSEGV) on macOS 10.14 (Mojave) if trying to start Windows 10 Guest
| Reported by: | rharting | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 5.2.18 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
Process: VirtualBoxVM [748] Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM Identifier: org.virtualbox.app.VirtualBoxVM Version: 5.2.18 (5.2.18) Code Type: X86-64 (Native) Parent Process: VBoxSVC [747] Responsible: VirtualBoxVM [748] User ID: 501
Date/Time: 2018-10-04 10:52:39.613 +0200 OS Version: Mac OS X 10.14 (18A391) Report Version: 12 Bridge OS Version: 3.0 (16P375) Anonymous UUID: F0AE1762-A39B-8B31-FA72-EBFAC4B9E51B
Sleep/Wake UUID: 1526540A-27B6-482C-8AB3-864E562E4740
Time Awake Since Boot: 4400 seconds Time Since Wake: 380 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010 Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [748]
VM Regions Near 0x10: -->
TEXT 0000000103da3000-0000000103dc5000 [ 136K] r-x/rwx SM=COW /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 VirtualBox.dylib 0x00000001044383e4 0x104338000 + 1049572 1 VirtualBox.dylib 0x000000010441c3b3 0x104338000 + 934835 2 VirtualBox.dylib 0x000000010471b8dd 0x104338000 + 4077789 3 org.qt-project.QtCoreVBox 0x0000000104f36808 QMetaObject::activate(QObject*, int, int, void) + 3048
Attachments (1)
Change History (2)
by , 5 years ago
| Attachment: | VBox_SIGSEGV_crash.log added |
|---|
Stack trace for SIGSEGV generated by macOS crash reporter
This isn't limited to Windows 10 guests, and it's persisted from 5.x through 6.0.16 (the latest as of this writing).
It happens for me with several different Linux guests and Win 10, and the crash seems to occur right when the VirtualBox "Manager" window re-gains focus after closing/suspending a guest.