Bug 623442 - [abrt] xulrunner- __pthread_mutex_lock: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
Summary: [abrt] xulrunner- __pthread_mutex_lock: Process /usr/lib64/xul...
Alias: None
Product: Fedora
Classification: Fedora
Component: xulrunner   
(Show other bugs)
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:80a4822ac33a51e6fd89a43b031...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-11 19:44 UTC by Matt Hooper
Modified: 2011-12-07 13:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-12-07 13:03:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (34.46 KB, text/plain)
2010-08-11 19:44 UTC, Matt Hooper
no flags Details

Description Matt Hooper 2010-08-11 19:44:05 UTC
abrt version: 1.1.5
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/xulrunner-1.9.2/plugin-container /home/matt/.mozilla/plugins/libflashplayer.so 27099 plugin
comment: I was about to add an attachment to another bug when Firefox (firefox-3.6.4-2.fc14) crashed and raised this abort and one for itself.
component: xulrunner
crash_function: __pthread_mutex_lock
executable: /usr/lib64/xulrunner-1.9.2/plugin-container
global_uuid: 80a4822ac33a51e6fd89a43b031acb027cba23ca
kernel: 2.6.35-0.55.rc6.git0.fc14.x86_64
package: xulrunner-
rating: 0
reason: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Rawhide)
time: 1281555684
uid: 500

Comment 1 Matt Hooper 2010-08-11 19:44:10 UTC
Created attachment 438272 [details]
File: backtrace

Comment 2 Martin Stransky 2011-12-07 13:03:01 UTC
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky@redhat.com).


Note You need to log in before you can comment on or make changes to this bug.