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

Bug #1289168 reported by yuk
This bug report is a duplicate of:  Bug #1371494: VirtualBox crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

login in

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: virtualbox-qt 4.3.6-dfsg-2
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Mar 7 10:57:27 2014
ExecutablePath: /usr/lib/virtualbox/VirtualBox
InstallationDate: Installed on 2014-02-19 (15 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140216)
ProcCmdline: /usr/lib/virtualbox/VirtualBox --comment dev2k --startvm 3616327f-9c36-4e0f-a299-c6fc6705ed93 --no-startvm-errormsgbox
SegvAnalysis:
 Segfault happened at: 0x7f0638001150: add %ah,%gs:0x39(%rax,%rax,1)
 PC (0x7f0638001150) in non-executable VMA region: 0x7f0638000000-0x7f0638021000 rw-p None
 source "%ah" ok
 destination "%gs:0x39(%rax,%rax,1)" (0xfe0c70002339) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason:
 executing writable VMA None
 writing unknown VMA
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:

Revision history for this message
yuk (sinoyster-s) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1287092, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.