gnome-shell crashed with SIGSEGV

Bug #1282871 reported by Swarnendu Biswas
82
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I was using Gnome shell and Google Hangouts, when the shell become unresponsive and crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 20 22:54:30 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f966cb0600f: test %rsi,(%rdx,%r8,8)
 PC (0x7f966cb0600f) ok
 source "%rsi" ok
 destination "(%rdx,%r8,8)" (0x7f966d0fd358) in non-writable VMA region: 0x7f966d0c0000-0x7f966d2c0000 ---p /usr/lib/x86_64-linux-gnu/libpulse.so.0.16.2
SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libpulse.so.0.16.2
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
gdmSessionLog:
 /etc/gdm/Xsession: Beginning session setup...
 localuser:biswass being added to access control list
 localuser:biswass being added to access control list
 Script for ibus started at run_im.

Revision history for this message
Swarnendu Biswas (swarna-cse) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 js::Shape::sweep (this=0x7f96482b4100) at /build/buildd/mozjs24-24.2.0/js/src/jspropertytree.cpp:229
 SweepPhase (sliceBudget=..., rt=0x28e2840) at /build/buildd/mozjs24-24.2.0/js/src/jsgc.cpp:3823
 IncrementalCollectSlice (rt=rt@entry=0x28e2840, budget=budget@entry=0, reason=reason@entry=JS::gcreason::TOO_MUCH_MALLOC, gckind=gckind@entry=js::GC_NORMAL) at /build/buildd/mozjs24-24.2.0/js/src/jsgc.cpp:4304
 GCCycle (rt=rt@entry=0x28e2840, incremental=incremental@entry=true, budget=budget@entry=0, gckind=gckind@entry=js::GC_NORMAL, reason=reason@entry=JS::gcreason::TOO_MUCH_MALLOC) at /build/buildd/mozjs24-24.2.0/js/src/jsgc.cpp:4422
 Collect (rt=0x28e2840, incremental=<optimized out>, budget=0, gckind=js::GC_NORMAL, reason=JS::gcreason::TOO_MUCH_MALLOC) at /build/buildd/mozjs24-24.2.0/js/src/jsgc.cpp:4558

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 gnome-shell (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 gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Tim Lunn (darkxst) wrote :

This should be fixed by gjs 1.40.1 update

information type: Private → Public
Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
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.