VirtualBox crashed with SIGSEGV

Bug #1352692 reported by Sergio Benjamim
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

Installed guest additions in linux guest SO, installed Extension Pack 4.3.10 (same version as virtual box system), added vboxusers to my user. Now every time I use Virtualbox, when I restart my laptop this apport window crash appears in the Host.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: virtualbox-qt 4.3.10-dfsg-1
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Tue Aug 5 01:20:51 2014
Disassembly: => 0x35: Cannot access memory at address 0x35
ExecutablePath: /usr/lib/virtualbox/VirtualBox
InstallationDate: Installed on 2014-05-26 (71 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcCmdline: /usr/lib/virtualbox/VirtualBox --comment Test\ i386 --startvm 0e26a6ca-1663-417f-bb54-28d77aefd141 --no-startvm-errormsgbox
SegvAnalysis:
 Segfault happened at: 0x35: Cannot access memory at address 0x35
 PC (0x00000035) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: virtualbox
StacktraceTop:
 ?? ()
 ?? () 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
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Sergio Benjamim (sergio-br2) wrote :
description: updated
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 #1352287, 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.