chromium-browser crashed with SIGSEGV in XQueryExtension()

Bug #919711 reported by Michael Tinsay
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I get a chromium-browser "crash" alert everytime I exit chromium. Chromium does not crash while I'm using it, just everytime I end the program.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 15.0.874.120~r108895-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Jan 22 00:11:32 2012
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
EcryptfsInUse: Yes
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111130.1)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --incognito
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f98c6a62c18 <XQueryExtension+40>: mov 0x968(%rdi),%rax
 PC (0x7f98c6a62c18) ok
 source "0x968(%rdi)" (0xffffffffcb673968) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XInitExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XextAddDisplay () from /usr/lib/x86_64-linux-gnu/libXext.so.6
 ?? () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/fglrx/libGL.so.1
Title: chromium-browser crashed with SIGSEGV in XQueryExtension()
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
Michael Tinsay (tinsami1) wrote :
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: New → 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.