Bug 623814 - [abrt] crash in firefox-3.5.11-1.fc12: Process /usr/lib/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.5.11-1.fc12: Process /usr/lib/firefox-3.5/firefox w...
Status: CLOSED DUPLICATE of bug 597119
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:24b87c93e03228e1e95a203079d...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-12 20:50 UTC by John Deighan
Modified: 2018-04-11 15:32 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2010-09-25 23:12:23 UTC

Attachments (Terms of Use)
File: backtrace (58.94 KB, text/plain)
2010-08-12 20:50 UTC, John Deighan
no flags Details
Part of the thread where crash happened (798 bytes, text/plain)
2010-09-25 23:12 UTC, Matěj Cepl
no flags Details

Description John Deighan 2010-08-12 20:50:05 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.5/firefox http://www.openculture.com/2010/08/richard_dawkins_john_lennox_debate_atheism.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+OpenCulture+%28Open+Culture%29&utm_content=Google+Reader
comment: see steps above.
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/firefox-3.5/firefox
global_uuid: 24b87c93e03228e1e95a203079da291601b6c8af
package: firefox-3.5.11-1.fc12
rating: 4
reason: Process /usr/lib/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. start firefox
2. cerf to 

3. start the movie


Comment 1 John Deighan 2010-08-12 20:50:09 UTC
Created attachment 438524 [details]
File: backtrace

Comment 2 Matěj Cepl 2010-09-25 23:12:03 UTC
Created attachment 449642 [details]
Part of the thread where crash happened

Comment 3 Matěj Cepl 2010-09-25 23:12:23 UTC

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

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