npviewer.bin crashed with SIGSEGV in pthread_mutex_lock()

Bug #456378 reported by Tarthen Brown
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nspluginwrapper (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: nspluginwrapper

I force quit FF when it went grey (stopped responding, rather) after I clicked a Youtube link (which crashed Flash and the browser), and apport came up.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 20 22:46:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
NonfreeKernelModules: nvidia
Package: nspluginwrapper 1.2.2-0ubuntu6
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-installer/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/2481-2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0xf6ffaded <pthread_mutex_lock+29>: mov 0xc(%esi),%edx
 PC (0xf6ffaded) ok
 source "0xc(%esi)" (0xf4beb030) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nspluginwrapper
StacktraceTop:
 pthread_mutex_lock () from /lib32/libpthread.so.0
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
Title: npviewer.bin crashed with SIGSEGV in pthread_mutex_lock()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Tarthen Brown (tarthen) wrote :
visibility: private → public
Revision history for this message
Francesco Usseglio (francescousseglio) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 192270, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:pthread_mutex_lock () from /lib32/libpthread.so.0
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in nspluginwrapper (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 an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

x11-common: installed version 1:7.4+3ubuntu6, latest version: 1:7.4+3ubuntu7

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 nspluginwrapper (Ubuntu):
status: Invalid → Confirmed
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.