chromium-browser crashed with SIGSEGV

Bug #709604 reported by Gary M
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: chromium-browser

cause unknown, only occurrence so far, hopefully trace shows something useful

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 96dffa43e3f34ec8f833d4966fb534ec
CheckboxSystem: 9c26adf6eed2f681ba41f94dd24c07e4
CrashDB: ubuntu
Date: Sat Jan 29 14:04:26 2011
Desktop-Session:
 DESKTOP_SESSION = gnome
 XDG_CONFIG_DIRS = None
 XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
DistroRelease: Ubuntu 9.10
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
Package: chromium-browser 9.0.597.83~r72435-0ubuntu1~ucd~beta1~karmic
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ --plugin-path=/usr/lib/gnash/libgnashplugin.so\ --lang=en-US\ --plugin-data-dir=/home/username/.config/chromium/Default\ --channel=4083.0xb818d220.1148492786
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-22.70-generic
SegvAnalysis:
 Segfault happened at: 0xb5d4026d: call *0x20(%edx)
 PC (0xb5d4026d) ok
 source "*0x20(%edx)" ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: chromium-browser
Stacktrace:
 #0 0xb5d4026d in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbffc237c
StacktraceTop: ?? ()
Tags: ubuntu-unr
ThirdParty: True
Title: chromium-browser crashed with SIGSEGV
Uname: Linux 2.6.31-22-generic i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare src
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Gary M (garym) wrote :
Gary M (garym)
tags: added: karmic
Gary M (garym)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : No launchpad retracing

Unsetting the need retracing tag, there is no retracer left running on that version of Ubuntu, the crash will need to be manually retraced

tags: removed: need-i386-retrace
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

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