chromium-browser crashed with SIGSEGV

Bug #727190 reported by Alex Mayorga on 2011-03-01
This bug affects 20 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)

Bug Description

Binary package hint: chromium-browser

This might be actually a crash on IcedTea-Web Plugin 1.0~20110122-0ubuntu1

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: chromium-browser 9.0.597.94~r73967-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
Architecture: amd64
CheckboxSubmission: ed5dbdfb54bf5043a043813a33527c9f
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
Date: Tue Mar 1 08:10:57 2011
 XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-2d:/etc/xdg
 XDG_DATA_DIRS = /usr/share/gnome-2d:/usr/share/gnome:/usr/local/share/:/usr/share/
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ --plugin-path=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/\ --lang=en-US\ --plugin-data-dir=/home/username/.config/chromium/Default\ --channel=2782.0x7faf62da4038.1493704879

 Segfault happened at: 0x7f828b4369c4: mov 0xe8(%rdi),%rax
 PC (0x7f828b4369c4) ok
 source "0xe8(%rdi)" (0x000000e8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2010-11-25 (95 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""

Alex Mayorga (alex-mayorga) wrote :

 push_back (this=0x0, destruction_observer=0x7f828e451800) at /usr/include/c++/4.5/bits/stl_vector.h:743
 AddObserver (this=0x0, destruction_observer=0x7f828e451800) at ./base/observer_list.h:118
 MessageLoop::AddDestructionObserver (this=0x0, destruction_observer=0x7f828e451800) at base/
 base::WaitableEventWatcher::StartWatching (this=0x7f828e451800, event=0x7f828e457130, delegate=0x7f828e4517f0) at base/
 IPC::SyncChannel::OnWaitableEventSignaled (this=0x7f828e4517e0, event=0x7f828e457130) at ipc/

Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Alex Mayorga (alex-mayorga) wrote :

This might be a symptom of Bug #727365

visibility: private → public
JustDevZero (justdevzero) wrote :

I can confirm it happens on Chromiun on Ubuntu 11.04.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Chad Miller (cmiller) wrote :

A lot has changed from v9 to v26. Please open a new bug with a new stack trace if this reoccurs.

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  Edit
Everyone can see this information.

Other bug subscribers