chromium-browser crashed with SIGSEGV in _XReply()

Bug #945325 reported by Mike Sandman
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Not really sure what I was doing to cause this.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.56~r121963-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Fri Mar 2 21:03:26 2012
Desktop-Session:
 DESKTOP_SESSION = ubuntu-2d
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --channel=2130.0xba4d8db0.116214045
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb2e7fcb7 <pthread_mutex_lock+23>: mov 0xc(%esi),%edi
 PC (0xb2e7fcb7) ok
 source "0xc(%esi)" (0x000000cc) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/fglrx/libGL.so.1
Title: chromium-browser crashed with SIGSEGV in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Mike Sandman (n8behavior) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop: ?? () from /tmp/tmpKUiLNW/usr/lib/fglrx/libGL.so.1

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Olivier Tilloy (osomon) wrote :

Closing now as this report wasn’t investigated timely and is now too old to be meaningful.
Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner.

Changed in chromium-browser (Ubuntu):
status: Confirmed → Won't Fix
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.