chromium-browser crashed with SIGSEGV in extensions::LazyBackgroundTaskQueue::ProcessPendingTasks()

Bug #1057921 reported by PioneerAxon
42
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Chromium Browser
Unknown
Unknown
chromium-browser (Debian)
Fix Released
Unknown
chromium-browser (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

It happened while trying to maximize window when the page was loading..

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: chromium-browser 20.0.1132.47~r144678-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Fri Sep 28 10:41:02 2012
Desktop-Session:
 DESKTOP_SESSION = gnome
 XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg
 XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
Disassembly: => 0x0: Cannot access memory at address 0x0
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120912)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 extensions::LazyBackgroundTaskQueue::ProcessPendingTasks(ExtensionHost*, Profile*, Extension const*) ()
 extensions::LazyBackgroundTaskQueue::Observe(int, content::NotificationSource const&, content::NotificationDetails const&) ()
 NotificationServiceImpl::Notify(int, content::NotificationSource const&, content::NotificationDetails const&) ()
 ExtensionHost::DidStopLoading() ()
Title: chromium-browser crashed with SIGSEGV in extensions::LazyBackgroundTaskQueue::ProcessPendingTasks()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin netdev plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/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
PioneerAxon (arth-svnit) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 extensions::LazyBackgroundTaskQueue::ProcessPendingTasks(ExtensionHost*, Profile*, Extension const*) ()
 extensions::LazyBackgroundTaskQueue::Observe(int, content::NotificationSource const&, content::NotificationDetails const&) ()
 NotificationServiceImpl::Notify(int, content::NotificationSource const&, content::NotificationDetails const&) ()
 ExtensionHost::DidStopLoading() ()

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
Revision history for this message
PioneerAxon (arth-svnit) wrote :

Happened when trying to switch to Apps menu from Most visited menu on blank page.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Changed in chromium-browser (Debian):
status: Unknown → New
Changed in chromium-browser (Debian):
status: New → Fix Released
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: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.