chromium-browser crashed with SIGSEGV in dri_st_framebuffer_flush_front()

Bug #858289 reported by Chris Bainbridge
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

chromium-browser crashed with SIGSEGV in dri_st_framebuffer_flush_front()

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: chromium-browser 13.0.782.215~r97094-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Sat Sep 24 15:35:08 2011
Desktop-Session:
 DESKTOP_SESSION = gnome-classic
 XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-classic:/etc/xdg
 XDG_DATA_DIRS = /usr/share/gnome-classic:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --channel=2343.0x7fe2b37dcb40.1696981894
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f19a2365244: mov 0x20(%rax),%rdi
 PC (0x7f19a2365244) ok
 source "0x20(%rax)" (0x213c000000020) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
 dri_st_framebuffer_flush_front (stfbi=<optimized out>, statt=<optimized out>) at dri_drawable.c:104
 dri_unbind_context (cPriv=<optimized out>) at dri_context.c:152
 driUnbindContext (pcp=0x7f19b34b8940) at ../common/dri_util.c:117
 glXMakeCurrentReadSGI () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
Title: chromium-browser crashed with SIGSEGV in dri_st_framebuffer_flush_front()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip floppy fuse lp lpadmin plugdev sambashare sudo video
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Chris Bainbridge (chris-bainbridge) 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
bingalls (bruce-ingalls) wrote :

If it helps, this happened to me, when I had open:
https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins
https://wiki.jenkins-ci.org/display/JENKINS/Plugins
Then tried opening a new tab with
https://github.com/jenkinsci/jenkins/blob/master/LICENSE.txt

Leafpad & Lxterminal (idle) were the only other apps running, on a recent install.

Revision history for this message
bingalls (bruce-ingalls) wrote :

Here is another way to reproduce the bug. Try installing and running
https://github.com/nicooprat/Css2Less
Pretty simple, but requires a few ruby gems, like sinatra.

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.