VirtualBox crashed with SIGSEGV

[LAZA]

I got this crash in an Xubuntu VM while i was working on the host.
False color in the VM let me think, this is a problem with the working BOINC - but got afterwards this crash report (i never got one if BOINC kills the VirtualBox screen).

Host: Xubuntu 14.04 64 bit
Guest: Xubuntu 14.04 32 bit

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: virtualbox-qt 4.3.10-dfsg-1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Apr 29 17:04:59 2014
Disassembly: => 0x35: Cannot access memory at address 0x35
ExecutablePath: /usr/lib/virtualbox/VirtualBox
ExecutableTimestamp: 1396842154
InstallationDate: Installed on 2014-03-16 (44 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140225)
ProcCmdline: /usr/lib/virtualbox/VirtualBox --comment Trusty --startvm bd94f663-cc25-4e85-b336-03b8bfa96d8b --no-startvm-errormsgbox
ProcCwd: /home/frank
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:

[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 #1304198, 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.