Bug 620098 - [abrt] crash in firefox-3.6.4-1.fc13: raise: Process /usr/lib/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in firefox-3.6.4-1.fc13: raise: Process /usr/lib/firefox-3.6/fir...
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox   
(Show other bugs)
Version: 13
Hardware: i686 Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:ed81ab00bd83835c75e4ee302af...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-31 21:21 UTC by Mads Kiilerich
Modified: 2011-06-29 12:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-29 12:42:44 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 (56.59 KB, text/plain)
2010-07-31 21:22 UTC, Mads Kiilerich
no flags Details

Description Mads Kiilerich 2010-07-31 21:21:48 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6/firefox -UILocale da
component: firefox
crash_function: raise
executable: /usr/lib/firefox-3.6/firefox
global_uuid: ed81ab00bd83835c75e4ee302af0cc100643e367
package: firefox-3.6.4-1.fc13
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 Mads Kiilerich 2010-07-31 21:22:05 UTC
Created attachment 435801 [details]
File: backtrace

Comment 2 Mads Kiilerich 2010-08-01 23:23:10 UTC
Assertion failure in:

Thread 1 (Thread 5746):
#7  0x0031ed98 in __assert_fail () from /lib/libc.so.6
#8  0x00c0bab6 in process_responses (dpy=<value optimized out>, 
    wait_for_first_event=0, current_error=0x0, current_request=0)
    at xcb_io.c:249
        reply = 0x0
        event = 0x0
        error = 0x0
        c = 0xb7671000
        __PRETTY_FUNCTION__ = "process_responses"
#9  0x00c0c3e7 in _XEventsQueued (dpy=0xb7601000, mode=2) at xcb_io.c:263
#10 0x00bf4988 in XPending (dpy=0xb7601000) at Pending.c:56
        ret_val = <value optimized out>
#11 0x00798949 in gdk_check_xpending (display=0xb766b140)
    at gdkevents-x11.c:154

The browser on this machine fails very often. It might be related to Java ...

(note to self: Rubens PC)

Comment 3 Mads Kiilerich 2010-08-01 23:42:54 UTC
looks a bit like bug 596510

Comment 4 Bug Zapper 2011-06-01 12:23:29 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 5 Bug Zapper 2011-06-29 12:42:44 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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