VirtualBox crashed with SIGSEGV

Bug #1273340 reported by martyfelker
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)
Confirmed
Medium
Unassigned

Bug Description

Appear every time I log in under every kernel. Ubuntu 14.04 All other information should be captured by the attachment

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: virtualbox-qt 4.3.2-dfsg-1ubuntu1
Uname: Linux 3.12.9-031209-generic x86_64
ApportVersion: 2.13.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Jan 27 00:12:07 2014
Disassembly: => 0x35: Cannot access memory at address 0x35
ExecutablePath: /usr/lib/virtualbox/VirtualBox
InstallationDate: Installed on 2014-01-26 (1 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130822)
ProcCmdline: /usr/lib/virtualbox/VirtualBox --comment Semplice --startvm 9ddee545-8fcc-4705-86bf-72eef72cdc56 --no-startvm-errormsgbox
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
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: Upgraded to trusty on 2014-01-26 (1 days ago)
UserGroups:

Revision history for this message
martyfelker (martyfelker-gmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 nsExceptionService::GetCurrentExceptionManager (this=0x228cd70, aCurrentScriptManager=0x7f88c689e6e0) at /build/buildd/virtualbox-4.3.2-dfsg/src/libs/xpcom18a4/xpcom/base/nsExceptionService.cpp:281
 DConnectStub::CallMethod (this=0x7f88a4006770, aMethodIndex=3, aInfo=0x2287c40, aParams=0x7f88c689e950) at /build/buildd/virtualbox-4.3.2-dfsg/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:2516
 PrepareAndDispatch (self=0x7f88a4006770, methodIndex=<optimized out>, args=<optimized out>, gpregs=<optimized out>, fpregs=0x7f88c689ea40) at /build/buildd/virtualbox-4.3.2-dfsg/src/libs/xpcom18a4/xpcom/reflect/xptcall/src/md/unix/xptcstubs_x86_64_linux.cpp:156
 SharedStub () from /tmp/apport_sandbox_1uWMFG/usr/lib/virtualbox/VBoxXPCOM.so

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in virtualbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu):
status: New → Confirmed
information type: Private → Public
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.