chromium-browser crashed with SIGABRT in raise()

Bug #934806 reported by Helge Jung
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Happened when I closed chromium.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: chromium-browser 16.0.912.77~r118311-0ubuntu0.11.10.1
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ChromiumPrefs:
 browser/check_default_browser = **unset** (no such key yet)
 extensions/settings =
  (no entry found in the Preferences file)
Date: Sat Feb 18 08:18:30 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 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:

Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: chromium-browser crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-10-15 (126 days ago)
UserGroups: adm admin cdrom chipcard dialout lpadmin plugdev sambashare vboxusers
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Helge Jung (youngage) wrote :
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.