unity8 crashed with SIGSEGV in __GI___pthread_mutex_lock()

Bug #1283298 reported by Thibaut Brandscheid
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity8 (Ubuntu)
New
Medium
Unassigned
virtualbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

I tried to start unity8 in VirtualBox typing 'unity(' into the terminal.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity8 7.84+14.04.20140221-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
Uname: Linux 3.13.0-10-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 22 00:54:41 2014
ExecutablePath: /usr/bin/unity8
InstallationDate: Installed on 2014-02-11 (10 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211)
ProcCmdline: unity8
SegvAnalysis:
 Segfault happened at: 0x7f15d4192414 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f15d4192414) ok
 source "0x10(%rdi)" (0x000020d8) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity8
StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66
 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
 start_thread (arg=0x7f15a810a700) at pthread_create.c:312
Title: unity8 crashed with SIGSEGV in __GI___pthread_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Thibaut Brandscheid (k1au3-is-37) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66
 stubSyncThreadProc (ThreadSelf=0x1c91020, pvUser=<optimized out>) at /build/buildd/virtualbox-4.3.6-dfsg/src/VBox/Additions/common/crOpenGL/load.c:898
 rtThreadMain (pThread=0x1c91020, NativeThread=<optimized out>, pszThreadName=<optimized out>) at /build/buildd/virtualbox-4.3.6-dfsg/src/VBox/Runtime/common/misc/thread.cpp:712
 rtThreadNativeMain (pvArgs=0x1c91020) at /build/buildd/virtualbox-4.3.6-dfsg/src/VBox/Runtime/r3/posix/thread-posix.cpp:324
 start_thread (arg=0x7f15a810a700) at pthread_create.c:312

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 unity8 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Michał Sawicz (saviq) wrote :

I'm afraid this very much looks like a vbox issue, not a unity8 one. Adding affects: virtualbox pending further investigation.

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.