VirtualBox crashed with SIGSEGV in nsCOMPtr_base::~nsCOMPtr_base()

[Gregory Bruce]

I use virtualbox a lot. It's been fine just until this one occassion. The VM's are windows xp. The exception happened while shutting down the VM. VIrtualbox thinks the VM shutdown completely, however Ubuntu said there was a problem. I'm running the Virtualbox from teh 14.04 repository (4,3,6), I update trusty daily

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: virtualbox-qt 4.3.6-dfsg-2
ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
Uname: Linux 3.13.0-21-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 2 22:55:40 2014
ExecutablePath: /usr/lib/virtualbox/VirtualBox
ProcCmdline: /usr/lib/virtualbox/VirtualBox --comment SQ155-11181-DEV-SQL2005 --startvm 4e394f34-3779-439a-8a8e-7ad78f042eb1 --no-startvm-errormsgbox
SegvAnalysis:
 Segfault happened at: 0x7f1014006870: add %al,(%rax)
 PC (0x7f1014006870) in non-executable VMA region: 0x7f1014000000-0x7f101402f000 rw-p None
 source "%al" ok
 destination "(%rax)" (0x7f1014001150) ok
 Stack memory exhausted (SP below stack segment)
SegvReason: executing writable VMA None
Signal: 11
SourcePackage: virtualbox
StacktraceTop:
 ?? ()
 nsCOMPtr_base::~nsCOMPtr_base() () from /usr/lib/virtualbox/VBoxXPCOM.so
 ?? () from /usr/lib/virtualbox/components/VBoxXPCOMIPCC.so
 ?? () from /usr/lib/virtualbox/VBoxXPCOM.so
 ?? () from /usr/lib/virtualbox/VBoxXPCOM.so
Title: VirtualBox crashed with SIGSEGV in nsCOMPtr_base::~nsCOMPtr_base()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1300851, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.