Opened 12 years ago
Closed 11 years ago
#11812 closed defect (fixed)
Mac OS X Host crash in OpenGL
| Reported by: | SnoopyLane | Owned by: | |
|---|---|---|---|
| Component: | 3D support | Version: | VirtualBox 4.2.12 |
| Keywords: | gleRunVertexSubmitImmediate ShCrOpenGL crash OpenGL | Cc: | |
| Guest type: | Linux | Host type: | Mac OS X |
Description
Host is VirtualBox 4.2.12 r84980, with extensions on MacBook Pro 2011 with Mountain Lion 10.8.3. Guest is Fedora 19 beta RC2, x86_64
I'm getting very frequent crashes, all are the same backtrace in the Mac .crash file.
Attachments (2)
Change History (6)
by , 12 years ago
| Attachment: | F19BRC2-2013-05-18-15-19-21.log.gz added |
|---|
by , 12 years ago
| Attachment: | VirtualBoxVM_2013-05-18-152103_rabbit.crash.gz added |
|---|
Mac OS X ".crash" file with backtraces
comment:1 by , 12 years ago
4.2.x has several known 3D issues on OSX host. OSX host 3D support should be significantly improved with the next major VBox release.
For now I can give a trunk test build for you to check whether your issue is fixed for you.
Please give it a try and let me know how it goes.
Note that you'd also need to update Guest Additions with those supplied with this test build.
!!! Note that the trunk is under heavy development now, so this build can NOT be used in production environment,
but ONLY for testing purposes. !!!
OSX host:
http://www.virtualbox.org/download/testcase/VirtualBox-4.2.51-85924-OSX.dmg
Extention pack:
http://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Extension_Pack-4.2.51-85924.vbox-extpack
comment:2 by , 12 years ago
Yes this seems to fix it.
Is there any way to get this fix backported to 4.2? Modern gnome desktops need 3D: running under 4.2 is pretty much useless: crashes with 3D acceleration, ungodly slow without it.
Or any ETA on when 4.3 will be available? I'm assuming that's the "next major VBox release" that you are referring to.
comment:4 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
4.3 is released now, and this should be fixed with it. Please give it a try and re-open this ticket if needed.
vbox.log