Bug 605463 - [abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib64/firefox-3.6/firefox ...
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:09c3ceaf6597aaa012e0db49483...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-18 02:11 UTC by Tony C
Modified: 2010-06-18 09:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-18 09:04:18 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (50.93 KB, text/plain)
2010-06-18 02:11 UTC, Tony C
no flags Details

Description Tony C 2010-06-18 02:11:14 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox https://secure.avaaz.org/en/whales_last_push/?cl=616456341&v=6634
comment: it's an install of a day, shouldn't be behaving like this
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
global_uuid: 09c3ceaf6597aaa012e0db49483c69429d825169
kernel: 2.6.33.5-124.fc13.x86_64
package: firefox-3.6.3-4.fc13
rating: 3
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.closed firefox
2.abrt opened and reported the crash
3.

Comment 1 Tony C 2010-06-18 02:11:17 UTC
Created attachment 424991 [details]
File: backtrace

Comment 2 Jan Horak 2010-06-18 09:04:18 UTC
Backtrace is unfortunately useless. If you are able to reproduce this bug feel free to reopen.


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