Bug 781709 - [abrt] firefox-3.6.24-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.24-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:17c19b4012257629afe8fa5d24e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-14 15:03 UTC by bumbi_abel@hotmail.com
Modified: 2012-02-14 15:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-14 15:35:27 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (61.57 KB, text/plain)
2012-01-14 15:03 UTC, bumbi_abel@hotmail.com
no flags Details

Description bumbi_abel@hotmail.com 2012-01-14 15:03:50 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 63044 bytes
cmdline: /usr/lib/firefox-3.6/firefox -UILocale sv-SE
component: firefox
Attached file: coredump, 247009280 bytes
crash_function: nsGenericElement::DestroyContent
executable: /usr/lib/firefox-3.6/firefox
kernel: 2.6.35.14-106.fc14.i686
package: firefox-3.6.24-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1326552500
uid: 500

How to reproduce
-----
1.I was online at www.blocket.se when it crashed
2.
3.

Comment 1 bumbi_abel@hotmail.com 2012-01-14 15:03:54 UTC
Created attachment 555234 [details]
File: backtrace

Comment 2 bumbi_abel@hotmail.com 2012-01-14 22:01:11 UTC
Package: firefox-3.6.24-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.I was online at www.blocket.se when it crashed
2.I was online at www.skanskan.se
3.

Comment 3 Martin Stransky 2012-02-14 15:35:27 UTC
Fedora 12 is no longer supported, please update to a new one.


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