Opened 11 years ago

Closed 8 years ago

#11407 closed defect (obsolete)

Virtualbox 4.2.6 crashes frequently in libQtCoreVBox

Reported by: sscdvp Owned by:
Component: other Version: VirtualBox 4.2.6
Keywords: Cc:
Guest type: all Host type: Solaris


I observer many crashes with virtualbox on S11.1 SRU3.4.

MDB shows the following:


ffff80ffbfffe320`realfree+0x3c() ffff80ffbfffe350`cleanfree+0x4a() ffff80ffbfffe380`_malloc_unlocked+0xdc() ffff80ffbfffe3a0`malloc+0x2c() ffff80ffbfffe3c0`_Znwm+0x1e() ffff80ffbfffe3f0`_ZN11QThreadPoolC1EP7QObject+0x24() ffff80ffbfffe410`_ZN11QThreadPool14globalInstanceEv+0x4e() ffff80ffbfffe430`_ZN16QCoreApplicationD2Ev+0x4d() ffff80ffbfffe4e0`_ZN12QApplicationD1Ev+0x572() ffff80ffbfffe690`TrustedMain+0x3da() ffff80ffbffff710 SUPR3HardenedMain+0x2e0() ffff80ffbffff720 _start+0x6c()


debugging core file of VirtualBox (64-bit) from boot198 file: /opt/VirtualBox/amd64/VirtualBox initial argv: /opt/VirtualBox/amd64/VirtualBox -session 10bdb5d90dcd9499d71354191836699892000 threading model: native threads status: process terminated by SIGSEGV (Segmentation Fault), addr= ffff80ffbf4efcf8

Change History (5)

comment:1 by sscdvp, 11 years ago

Another one:


ffff80ffbfffe430`realfree+0x3c() ffff80ffbfffe450`_free_unlocked+0x78() ffff80ffbfffe470`free+0x32() ffff80ffbfffe490`_ZN7QString4freeEPNS_4DataE+0x1a() ffff80ffbfffe4c0`_ZN5QListI7QStringE4freeEPN9QListData4DataE+0x40( ) ffff80ffbfffe4e0`_ZN22QSessionManagerPrivateD0Ev+0x39() ffff80ffbfffe560`_ZN7QObjectD2Ev+0x392() ffff80ffbfffe580`_ZN15QSessionManagerD0Ev+0x52() ffff80ffbfffe630`_ZN12QApplicationD1Ev+0x4a2() ffff80ffbfffe7e0`TrustedMain+0x3da() ffff80ffbffff860 SUPR3HardenedMain+0x2e0() ffff80ffbffff870 _start+0x6c()

comment:2 by Frank Mehnert, 11 years ago

Doesn't say me anything. How to reproduce this crash?

comment:3 by sscdvp, 11 years ago

It appears on low memory condition.

in reply to:  2 comment:4 by sscdvp, 11 years ago

Replying to frank:

Doesn't say me anything. How to reproduce this crash?

Firstly start VM in headless mode. Then you can try to run Virtualbox GUI. Try to do something e.g. VM restart

comment:5 by aeichner, 8 years ago

Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use