Bug 610492 - [abrt] crash in firefox-3.6.4-1.fc13: PR_JoinThread: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.6.4-1.fc13: PR_JoinThread: Process /usr/lib/firefox...
Status: CLOSED DUPLICATE of bug 605894
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
(Show other bugs)
Version: 13
Hardware: i686 Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:ef35c518ec6ec510952317e7324...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-02 08:46 UTC by cyrushmh
Modified: 2010-11-09 14:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 14:37:34 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 (28.26 KB, text/plain)
2010-07-02 08:46 UTC, cyrushmh
no flags Details

Description cyrushmh 2010-07-02 08:46:19 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6/firefox http://World-Cup-Winners.com/?id=5c5c5ba6ce149301a0482cd6c3b40bb5
component: firefox
crash_function: PR_JoinThread
executable: /usr/lib/firefox-3.6/firefox
global_uuid: ef35c518ec6ec510952317e7324b704552757c23
package: firefox-3.6.4-1.fc13
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 cyrushmh 2010-07-02 08:46:24 UTC
Created attachment 428773 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:37:34 UTC

*** This bug has been marked as a duplicate of bug 605894 ***

Comment 3 Karel Klíč 2010-11-09 14:37:34 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #605894.

Sorry for the inconvenience.

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