chromium-browser crashed with SIGSEGV

Bug #952411 reported by Michał Krawczyk
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I was trying to install an extension for Chromium browser and I got a bug report.

Relese - Xubuntu 12.04 Beta 1

Package - 5.1.12

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.78~r125577-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sun Mar 11 18:31:46 2012
Desktop-Session:
 DESKTOP_SESSION = xubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share
DetectedPlugins:
 => Remoting Viewer
    - enabled = True
    - path = internal-remoting-viewer
 => Remoting Viewer
    - enabled = True
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228)
InstalledPlugins:

ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --channel=11574.0xb9d8cb10.129471179
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x5a1108: sub %ah,0xa9ffff(%ecx)
 PC (0x005a1108) ok
 source "%ah" ok
 destination "0xa9ffff(%ecx)" (0x00a9ffff) in non-writable VMA region: 0x00a89000-0x00aa6000 r-xp /usr/lib/i386-linux-gnu/libatk-1.0.so.0.20400.1
SegvReason: writing VMA /usr/lib/i386-linux-gnu/libatk-1.0.so.0.20400.1
Signal: 11
SourcePackage: chromium-browser
Stacktrace:
 #0 0x005a1108 in ?? () from /lib/i386-linux-gnu/libresolv.so.2
 No symbol table info available.
 Cannot access memory at address 0x48f53888
StacktraceTop: ?? () from /lib/i386-linux-gnu/libresolv.so.2
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-11 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Michał Krawczyk (mkkrawiec) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x005a1108 in ?? () from /tmp/tmp8g4Tl6/lib/i386-linux-gnu/libresolv.so.2
 No symbol table info available.
 Cannot access memory at address 0x48f53888
StacktraceTop: ?? () from /tmp/tmp8g4Tl6/lib/i386-linux-gnu/libresolv.so.2

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
visibility: private → public
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.