chromium-browser crashed with SIGSEGV in unity_webapps_application_repository_resolve_url().

Bug #1060091 reported by Víctor R. Ruiz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Undecided
Alexandre Abreu

Bug Description

1. Open Chromium.
2. Go to launchpad.net (without integration already accepted).

Expected result: Integration dialog prompt.

This crash error appears instead.

This is using the daily PPA:

unity-chromium-extension 2.4+bzr182+25-0ubuntu0+116

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
Date: Tue Oct 2 10:39:11 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 7.9G 3.2G 4.4G 42% /\nudev devtmpfs 993M 4.0K 993M 1% /dev\ntmpfs tmpfs 401M 768K 400M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 1002M 296K 1002M 1% /run/shm\nnone tmpfs 100M 0 100M 0% /run/user\n'

 Inodes:
 b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 512K 164K 349K 32% /\nudev 249K 461 248K 1% /dev\ntmpfs 251K 378 251K 1% /run\nnone 251K 3 251K 1% /run/lock\nnone 251K 10 251K 1% /run/shm\nnone 251K 1 251K 1% /run/user\n'
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64+mac (20121001)
LocalLibraries: /home/ubuntu/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.4.1_0/libunity_npapi_plugin.so
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ --plugin-path=/home/username/.config/chromium/Default/Extensions/pmoflmbbcfgacopiikdcpmbiellfihdg/2.4.1_0/libunity_npapi_plugin.so\ --lang=en-US\ --channel=16108.9.1732555380
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f4f52a41b70: mov (%rbx),%rsi
 PC (0x7f4f52a41b70) ok
 source "(%rbx)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libunity-webapps-repository.so.0
 unity_webapps_application_repository_resolve_url () from /usr/lib/x86_64-linux-gnu/libunity-webapps-repository.so.0
 unity_webapps_application_repository_resolve_url_as_json () from /usr/lib/x86_64-linux-gnu/libunity-webapps-repository.so.0
 unity_webapps_binding_application_repository_resolve_url_as_json (instance=<optimized out>, npobject=<optimized out>, args=<optimized out>, argCount=<optimized out>) at unity-webapps-repository-binding.c:153
 NPClass_Invoke (result=0x7fff1d9f86b0, argCount=2, args=0x7f4f668b4cc0, name=<optimized out>, npobj=0x7f4f668c9b90) at unity-webapps-base-js-object.c:377
Title: chromium-browser crashed with SIGSEGV in unity_webapps_application_repository_resolve_url()
UpgradeStatus: No upgrade log present (probably fresh install)
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'

Revision history for this message
Víctor R. Ruiz (vrruiz) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /tmp/tmpGYxg8l/lib64/ld-linux-x86-64.so.2
 ?? ()
 ?? ()

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):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

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 libstdc++6: package version 4.7.2-2ubuntu1 dbgsym version 4.6.3-1ubuntu5
outdated debug symbol package for libtxc-dxtn-s2tc0: package version 0~git20110809-3 dbgsym version 0~git20110809-2.1

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!

tags: removed: need-amd64-retrace
Changed in chromium-browser (Ubuntu):
assignee: nobody → Alexandre Abreu (abreu-alexandre)
status: Invalid → New
visibility: private → public
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.