plugin-container crashed with SIGSEGV in __pthread_mutex_lock()

Bug #631339 reported by jan.san@libero.it
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: firefox

While using firefox

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: firefox 3.6.9+build1+nobinonly-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Sep 6 08:56:31 2010
ExecutablePath: /usr/lib/firefox-3.6.9/plugin-container
FirefoxPackages:
 firefox 3.6.9+build1+nobinonly-0ubuntu1
 firefox-gnome-support 3.6.9+build1+nobinonly-0ubuntu1
 firefox-branding 3.6.9+build1+nobinonly-0ubuntu1
 abroswer N/A
 abrowser-branding N/A
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/lib/firefox-3.6.9/plugin-container /usr/lib/flashplugin-installer/libflashplayer.so 3213 plugin true
ProcEnviron:
 PATH=(custom, user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc67fe7d634 <__pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7fc67fe7d634) ok
 source "0x10(%rdi)" (0x7fc66cee0078) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: firefox
StacktraceTop:
 __pthread_mutex_lock (mutex=0x7fc66cee0068) at pthread_mutex_lock.c:50
 ?? ()
 ?? ()
 ?? ()
 __run_exit_handlers (status=1) at exit.c:78
Title: plugin-container crashed with SIGSEGV in __pthread_mutex_lock()
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin mythtv netdev plugdev polkituser sambashare tape video

Revision history for this message
jan.san@libero.it (jan-san) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in firefox (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:

dpkg: installed version 1.15.8.4ubuntu2, latest version: 1.15.8.4ubuntu3
libsqlite3-0: installed version 3.7.0.1-1, latest version: 3.7.2-1
libglib2.0-0: installed version 2.25.15-0ubuntu1, latest version: 2.25.15-0ubuntu2
libc-bin: installed version 2.12.1-0ubuntu2, latest version: 2.12.1-0ubuntu4
libpixman-1-0: installed version 0.18.2-1ubuntu1, latest version: 0.18.4-1
libfreetype6: installed version 2.4.2-1, latest version: 2.4.2-2
libc6: installed version 2.12.1-0ubuntu2, latest version: 2.12.1-0ubuntu4

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
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

How did you even manage to report this? We blacklisted Firefox in Apport now.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Oh, plugin-container is not blacklisted....

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.