chromium-browser crashed with SIGSEGV in brw_update_renderbuffer_surface()

Bug #932481 reported by Logan Rosen on 2012-02-15
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Medium
Unassigned

Bug Description

This happened after I enabled WebGL in Google Maps. My graphics/GUI in Ubuntu crashed as well, and I am writing this report with just Chromium open.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 16.0.912.77~r118311-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 14 20:30:11 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/
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 (20120201.1)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --channel=18449.0x7ff51d727200.2127059623
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fce33a5b76e: mov 0x218(%rax),%rbp
 PC (0x7fce33a5b76e) ok
 source "0x218(%rax)" (0x00000218) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 brw_upload_state () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 brw_draw_prims () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/libdricore.so
Title: chromium-browser crashed with SIGSEGV in brw_upload_state()
UpgradeStatus: Upgraded to precise on 2012-02-11 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""

Logan Rosen (logan) wrote :

StacktraceTop:
 brw_update_renderbuffer_surface (brw=0x7fce4584e030, rb=0x7fce44a318c0, unit=0) at brw_wm_surface_state.c:905
 brw_update_renderbuffer_surfaces (brw=0x7fce4584e030) at brw_wm_surface_state.c:1002
 brw_upload_state (brw=0x7fce4584e030) at brw_state_upload.c:504
 brw_try_draw_prims (max_index=<optimized out>, min_index=<optimized out>, ib=0x7fff026395a0, nr_prims=1, prim=0x7fff026395c0, arrays=0x7fce457655a8, ctx=0x7fce4584e030) at brw_draw.c:521
 brw_draw_prims (ctx=0x7fce4584e030, arrays=0x7fce457655a8, prim=0x7fff026395c0, nr_prims=1, ib=0x7fff026395a0, index_bounds_valid=<optimized out>, min_index=4294967295, max_index=4294967295, tfb_vertcount=0x0) at brw_draw.c:605

Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
summary: - chromium-browser crashed with SIGSEGV in brw_upload_state()
+ chromium-browser crashed with SIGSEGV in
+ brw_update_renderbuffer_surface()
tags: removed: need-amd64-retrace
Logan Rosen (logan) on 2012-02-15
visibility: private → public
Launchpad Janitor (janitor) wrote :

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

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
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  Edit
Everyone can see this information.

Other bug subscribers