Ticket #11812 (closed defect: fixed)

Opened 2 years ago

Last modified 22 months ago

Mac OS X Host crash in OpenGL

Reported by: SnoopyLane Owned by:
Priority: major Component: 3D support
Version: VirtualBox 4.2.12 Keywords: gleRunVertexSubmitImmediate ShCrOpenGL crash OpenGL
Cc: Guest type: Linux
Host type: Mac OS X


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.


F19BRC2-2013-05-18-15-19-21.log.gz Download (15.5 KB) - added by SnoopyLane 2 years ago.
VirtualBoxVM_2013-05-18-152103_rabbit.crash.gz Download (14.7 KB) - added by SnoopyLane 2 years ago.
Mac OS X ".crash" file with backtraces

Change History

Changed 2 years ago by SnoopyLane


Changed 2 years ago by SnoopyLane

Mac OS X ".crash" file with backtraces

comment:1 Changed 2 years ago by misha

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:

Extention pack:

comment:2 Changed 2 years ago by SnoopyLane

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:3 Changed 23 months ago by bulletmark

Also see ticket #12107.

comment:4 Changed 22 months ago by misha

  • Status changed from new to closed
  • Resolution set to fixed

4.3 is released now, and this should be fixed with it. Please give it a try and re-open this ticket if needed.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use