chromium-browser crashed with SIGSEGV in UnityWebappsContextRaiseCallback_dispatcher()

[Jason Warner]

Had webapps open, but then closed them. Apps stayed around in launcher and alt+tab after closing them. When I tried to click on the app in the launcher, it crashed webapps plugin.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: chromium-browser 20.0.1132.47~r144678-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 3 20:15:40 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/
DiskUsage:
 b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda1 ext4 114G 79G 30G 73% /\nudev devtmpfs 3.9G 4.0K 3.9G 1% /dev\ntmpfs tmpfs 1.6G 908K 1.6G 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 3.9G 5.4M 3.9G 1% /run/shm\ncgroup tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup\n'

 Inodes:
 b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 7.3M 992K 6.3M 14% /\nudev 981K 507 981K 1% /dev\ntmpfs 984K 448 984K 1% /run\nnone 984K 3 984K 1% /run/lock\nnone 984K 13 984K 1% /run/shm\ncgroup 984K 9 984K 1% /sys/fs/cgroup\n'
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
LocalLibraries: /home/jason/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.0_0/libunity_npapi_plugin.so
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ --plugin-path=/home/username/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.0_0/libunity_npapi_plugin.so\ --lang=en-US\ --channel=2502.31.927173068
ProcEnviron:

Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? ()
 UnityWebappsContextRaiseCallback_dispatcher (context=<optimized out>, file=0x0, user_data=0x7fd13025bc60) at unity-webapps-binding.c:478
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: chromium-browser crashed with SIGSEGV in UnityWebappsContextRaiseCallback_dispatcher()
UpgradeStatus: Upgraded to quantal on 2012-07-23 (42 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command = b'/opt/google/chrome/google-chrome %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/opt/google/chrome/google-chrome %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'Faenza-Dark\n'/desktop/gnome/interface/gtk_theme = b'Adwaita\n'

[Apport retracing service (apport)]

StacktraceTop:
 NPObjectProxy::NPInvokePrivate(_NPP*, NPObject*, bool, void*, _NPVariant const*, unsigned int, _NPVariant*) ()
 (anonymous namespace)::NPN_InvokeDefaultPatch(_NPP*, NPObject*, _NPVariant const*, unsigned int, _NPVariant*) ()
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu3 dbgsym version 3.16-1ubuntu2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Ursula Junque (ursinha)]

I hit this bug three times since I upgraded from Precise to Quantal. Maybe it's invalid for chromium-browser, but valid in unity webapps context?