chromium-browser crashed with SIGSEGV

Bug #1380212 reported by Stephen Michael Kellat
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

chromium crashed out while gracelessly shutting down.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Oct 12 00:12:37 2014
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2014-06-14 (119 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=3200.0.945800868\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,15,22\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x1002\ --gpu-device-id=0x9830\ --gpu-driver-vendor\ --gpu-driver-versi
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: Upgraded to utopic on 2014-09-22 (19 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
modified.conffile..etc.default.chromium.browser: [deleted]

Revision history for this message
Stephen Michael Kellat (skellat) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 pipe_sampler_view_reference (view=0x0, ptr=0x19e0e63ccbc8) at ../../../../src/gallium/auxiliary/util/u_inlines.h:151
 st_texture_release_all_sampler_views (stObj=stObj@entry=0x19e0e6352400) at ../../../../src/mesa/state_tracker/st_texture.c:515
 st_DeleteTextureObject (ctx=0x19e0e6324000, texObj=0x19e0e6352400) at ../../../../src/mesa/state_tracker/st_cb_texture.c:158
 free_shared_state (shared=<optimized out>, ctx=<optimized out>) at ../../../../src/mesa/main/shared.c:298

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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.