*** This bug is a duplicate of bug 1057921 ***
    https://bugs.launchpad.net/bugs/1057921

** This bug has been marked a duplicate of bug 1057921
   chromium-browser crashed with SIGSEGV in 
extensions::LazyBackgroundTaskQueue::ProcessPendingTasks()

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1063819

Title:
  chromium-browser crashed with SIGSEGV

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Closest matching bug was from earlier this year and was "fix released"

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: chromium-browser 20.0.1132.47~r144678-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Oct  8 10:39:33 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 12.10 "Quantal Quetzal" - Beta amd64 (20120925)
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f7c7e643480:        add    %ch,0x7f7c7e7f(%rdi)
   PC (0x7f7c7e643480) in non-executable VMA region: 
0x7f7c7e54d000-0x7f7c7f274000 rw-p [heap]
   source "%ch" ok
   destination "0x7f7c7e7f(%rdi)" (0x7f7cfcd7a77f) not located in a known VMA 
region (needed writable region)!
  SegvReason:
   executing writable VMA [heap]
   writing unknown VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: Upgraded to quantal on 2012-10-04 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%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'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1063819/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to