chromium-browser crashed with SIGSEGV in _XSend()

Bug #848872 reported by Patrik Sengbusch
68
This bug affects 16 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

hromium-browser crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: chromium-browser 15.0.871.0~svn20110904r99583-0ubuntu1~ucd1
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic-pae 3.0.4
Uname: Linux 3.0.0-11-generic-pae i686
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
CrashCounter: 1
CrashDB: ubuntu
Date: Tue Sep 13 13:15:33 2011
Desktop-Session:
 DESKTOP_SESSION = default
 XDG_CONFIG_DIRS = /etc/xdg/xdg-default:/etc/xdg
 XDG_DATA_DIRS = /usr/share/default:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --channel=1773.0xbb404b00.38505649\ --disable-gl-multisampling
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb3d80f65 <_XSend+37>: mov 0x0(%ebp),%esi
 PC (0xb3d80f65) ok
 source "0x0(%ebp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 _XSend () from /usr/lib/i386-linux-gnu/libX11.so.6
 _XFlush () from /usr/lib/i386-linux-gnu/libX11.so.6
 XQueryExtension () from /usr/lib/i386-linux-gnu/libX11.so.6
 XInitExtension () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
ThirdParty: True
Title: chromium-browser crashed with SIGSEGV in _XSend()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Patrik Sengbusch (patrik-ps) wrote :
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
H-w25-c25 (h-w25-c25) wrote :

when i use it, this happened.

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

I'm going to close this bug report as their is nothing else we can do with this old report in a now unsupported version of Ubuntu.

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Oops, sorry, can anyone still reproduce this with an up-to-date Chromium?

Changed in chromium-browser (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]

Changed in chromium-browser (Ubuntu):
status: Incomplete → Expired
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.