chromium-browser crashed with SIGABRT

Bug #1223455 reported by Jean-Baptiste Lallement
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Crashed while launching 2 instances of chromium in background

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: chromium-browser 29.0.1547.65-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0
Uname: Linux 3.11.0-6-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 10 12:40:05 2013
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/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
InstallationDate: Installed on 2013-09-03 (6 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
MarkForUpload: True
ProcCmdline: chromium-browser\ --window-size=400,200\ --window-position=100,100\ --user-data-dir=profile_storage
Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: chromium-browser crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
tags: added: qa-manual-testing
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 base::debug::BreakDebugger () at base/debug/debugger_posix.cc:247
 (anonymous namespace)::SetupSockAddr (path=..., addr=0x7fffcc48b780) at chrome/browser/process_singleton_linux.cc:209
 ConnectSocket (cookie_path=..., socket_path=..., socket=<synthetic pointer>) at chrome/browser/process_singleton_linux.cc:369
 ProcessSingleton::NotifyOtherProcessWithTimeout (this=this@entry=0x4ee345d89f8, cmd_line=..., timeout_seconds=timeout_seconds@entry=20, kill_unresponsive=kill_unresponsive@entry=true) at chrome/browser/process_singleton_linux.cc:717
 ProcessSingleton::NotifyOtherProcessWithTimeoutOrCreate (this=0x4ee345d89f8, command_line=..., timeout_seconds=20) at chrome/browser/process_singleton_linux.cc:840

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
information type: 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.