chromium-browser crashed with SIGSEGV

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

Bug Description

Chromium crashed on G.Reader page.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 25.0.1364.160-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
Uname: Linux 3.2.0-40-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 10 13:34:28 2013
Desktop-Session:
 DESKTOP_SESSION = pantheon
 XDG_CONFIG_DIRS = /etc/xdg/xdg-pantheon:/etc/xdg
 XDG_DATA_DIRS = /usr/share/pantheon:/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 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f18d451d83c: mov 0x0(%rbp),%rax
 PC (0x7f18d451d83c) ok
 source "0x0(%rbp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors: gnome-session[1969]: WARNING: Failed to start app: Unable to start application: Не удалось выполнить процесс-потомок «docky» (Нет такого файла или каталога)
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Alex N (m11g5wje9-i-5lmmq9sw5) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 AlternateNavURLFetcher::ShowInfobarIfPossible() ()
 base::internal::Invoker<2, base::internal::BindState<base::internal::RunnableAdapter<void (net::URLFetcherCore::*)(base::TimeDelta)>, void (net::URLFetcherCore*, base::TimeDelta), void (net::URLFetcherCore*, base::TimeDelta)>, void (net::URLFetcherCore*, base::TimeDelta)>::Run(base::internal::BindStateBase*) ()
 MessageLoop::RunTask(base::PendingTask const&) ()
 MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) ()
 MessageLoop::DoWork() ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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
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.