Opened 8 years ago
Last modified 8 years ago
#15959 new defect
Save state crashes when 3D acceleration is enabled
| Reported by: | eoftedal | Owned by: | |
|---|---|---|---|
| Component: | 3D support | Version: | VirtualBox 5.1.6 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Mac OS X |
Description
Process: VirtualBoxVM [60994]
Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier: org.virtualbox.app.VirtualBoxVM
Version: 5.1.6 (5.1.6)
Code Type: X86-64 (Native)
Parent Process: VBoxSVC [60975]
Responsible: VirtualBoxVM [60994]
User ID: 501
Date/Time: 2016-09-20 08:55:59.868 +0200
OS Version: Mac OS X 10.11.6 (15G1004)
Report Version: 11
Anonymous UUID: D9DBB08D-4C4D-8B25-6CC5-48A55E634305
Sleep/Wake UUID: A19E6FC4-4C2A-4961-BD52-A4258770AA33
Time Awake Since Boot: 390000 seconds
Time Since Wake: 6400 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 0x00000000414b0000
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0x414b0000:
-->
__TEXT 00000001057e2000-00000001057e9000 [ 28K] r-x/rwx SM=COW /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM
Application Specific Information:
Performing @selector(_close:) from sender _NSThemeCloseWidget 0x7fce42ae37f0
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtCoreVBox 0x000000010686e7a0 QHashData::free_helper(void (*)(QHashData::Node*)) + 64
1 org.qt-project.QtGuiVBox 0x0000000106ea28e5 QTextFormatCollection::~QTextFormatCollection() + 69
2 org.qt-project.QtGuiVBox 0x0000000106eba708 0x106d7e000 + 1296136
3 org.qt-project.QtGuiVBox 0x0000000106eba79e 0x106d7e000 + 1296286
4 org.qt-project.QtCoreVBox 0x00000001069e4201 QObject::~QObject() + 1841
Attachments (1)
Change History (2)
by , 8 years ago
| Attachment: | Virtualbox.crash added |
|---|
comment:1 by , 8 years ago
Do you mind opening a thread in the forums so we can discuss the background of this? I really prefer it there, since the bug report is not "polluted" with back and forth discussions and secondly, more people in the forums, more eyes, more potential ideas and solutions.
Note:
See TracTickets
for help on using tickets.


crashlog