Ticket #6920 (closed defect: obsolete)

Opened 7 years ago

Last modified 4 years ago

Crash [@ sseCGSConvertXXXX8888Mask]

Reported by: timeless Owned by:
Priority: major Component: GUI
Version: VirtualBox 3.2.2 Keywords:
Cc: Guest type: Windows
Host type: Mac OS X

Description (last modified by frank) (diff)

  • Guest: w7x86 enterprise
  • Host: OS X 10.6.3
Thread 0 Crashed:  Dispatch queue:
0        	0x912e5310 sseCGSConvertXXXX8888Mask + 112
1        	0x911f6dfe argb32_image + 4014
2   libRIP.A.dylib                	0x94478722 ripd_Mark + 295
3   libRIP.A.dylib                	0x9446dc55 ripl_BltImage + 1593
4   libRIP.A.dylib                	0x9446d38f ripc_RenderImage + 269
5   libRIP.A.dylib                	0x9446a96e ripc_DrawImage + 2697
6        	0x911f1cdc CGContextDrawImage + 450
7   VirtualBox.dylib              	0x011e50cc UIFrameBufferQuartz2D::paintEvent(QPaintEvent*) + 748
8   VirtualBox.dylib              	0x01189083 UIMachineView::paintEvent(QPaintEvent*) + 67
9   QtGuiVBox                     	0x015650be QWidget::event(QEvent*) + 2686


VirtualBoxVM_2010-06-07-151616_localhost.crash Download (37.2 KB) - added by timeless 7 years ago.
OS X crash report

Change History

Changed 7 years ago by timeless

OS X crash report

comment:1 Changed 7 years ago by frank

Any improvement with VBox 3.2.6?

comment:2 Changed 7 years ago by timeless

I haven't used 3.2.6 as much as I've used previous versions. Unfortunately, it seems like something ate my crash report logs (at least for VirtualBox), as I can't find *any* of them. It's possible they were eaten by my update from OS X 10.6.3 to OS X 10.6.4 - dunno :(.

there are a couple of VirtualBox machine logs which don't end in TERMINATED, but they seem to be before 3.2.6.

I basically have a couple of tasks for VirtualBox:

  1. use w7 to build or debug Firefox
  2. use w7 as a vpn client
  3. use w7 to compile stuff for Symbian
  4. use OpenSolaris to stage stuff
  5. use Maemo/Mer/Moblin/MeeGo to develop small stuff
  • atm OpenSolaris itself is having issues when i try to update it (i think this is a combination of not enough ram allocated to the vm, the vm being too out of date, the host ZFS causing the host system to use >1gb of ram for the darwin kernel, and poor disk performance [the update process times out]), which means i don't really get much use out of it
  • my w7 Symbian stuff is shelved because the Symbian engineers are too busy
  • my w7 builds for Firefox are suffering from ram starvation and disk performance (a while ago i switched from 10.5 to 10.6 and changed ZFS copies=1 to copies=2 because my previous hdd failed, but this kills performance especially in Windows w/ disk swap)
  • i did at one point do some vpn stuff in w7 but the AV system gave me so much pain that i try to avoid w7 entirely
  • i do still do a bit of WinDbg stuff in w7, but i try to avoid it
  • my personal priorities have shifted so i haven't spent much time on the Mer stuff

Basically none of these things are VirtualBox's fault. A number of them are self inflicted (zfs copies=2) and fixable. I've just *now* set copies=1 for my HardDisks folder, which I'd hope would improve performance of my VMs (at the expense of data fidelity).

I think that I try to enable 2d/3d acceleration in my vms (one or both of which have been marked as experimental), it'd be nice if someone could inform me whether the crash here is in a code path which is limited to an acceleration option or whether it's generic.

comment:3 Changed 4 years ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use