VBoxSVC crashed with SIGSEGV in malloc()

[Felix Möller]

This happened when shutting down a virtual machine that was accessing a raw disk image. This does not happen every time.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: virtualbox 4.1.2-dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Sun Sep 11 03:30:25 2011
ExecutablePath: /usr/lib/virtualbox/VBoxSVC
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: /usr/lib/virtualbox/VBoxSVC --auto-shutdown
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f22f5b4cce8: mov 0x8(%r14),%rax
 PC (0x7f22f5b4cce8) ok
 source "0x8(%r14)" (0x7f21e80396c7) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: virtualbox
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 malloc () from /lib/x86_64-linux-gnu/libc.so.6
 operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /usr/lib/virtualbox/components/VBoxXPCOMIPCC.so
 ?? () from /usr/lib/virtualbox/components/VBoxXPCOMIPCC.so
Title: VBoxSVC crashed with SIGSEGV in malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 _int_malloc (av=0x7f22e8000020, bytes=32) at malloc.c:4304
 __GI___libc_malloc (bytes=32) at malloc.c:3660
 operator new (sz=32) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:52
 IPC_OnMessageAvailable (msg=0x7f22e8000be0) at /build/buildd/virtualbox-4.1.2-dfsg/src/libs/xpcom18a4/ipc/ipcd/client/src/ipcdclient.cpp:1374
 ConnRead (s=0x2073c80) at /build/buildd/virtualbox-4.1.2-dfsg/src/libs/xpcom18a4/ipc/ipcd/client/src/ipcConnectionUnix.cpp:257

[Launchpad Janitor (janitor)]

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