Bug 536981 - [abrt] crash detected in firefox-3.5.4-1.fc12
Summary: [abrt] crash detected in firefox-3.5.4-1.fc12
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libxcb
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 528388 539341 540136 541051 542739 542838 543074 543763 545230 554114 572345 641959 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-12 02:26 UTC by Derek Schmidt
Modified: 2018-04-11 08:51 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-28 14:16:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (59.34 KB, text/plain)
2009-11-12 02:26 UTC, Derek Schmidt 		no flags Details
View All

Description Derek Schmidt 2009-11-12 02:26:22 UTC 
abrt detected a crash.

Attached file: backtrace
cmdline: /usr/lib/firefox-3.5.4/firefox
component: firefox
executable: /usr/lib/firefox-3.5.4/firefox
kernel: 2.6.31.5-127.fc12.i686
package: firefox-3.5.4-1.fc12
rating: 2
reason: Process was terminated by signal 6
Comment 1 Derek Schmidt 2009-11-12 02:26:24 UTC 
Created attachment 369126 [details]
File: backtrace
Comment 2 Martin Stransky 2009-11-12 07:58:51 UTC 
Is there any reproducer?
Comment 3 Derek Schmidt 2009-11-13 13:42:27 UTC 
Not that I know of, to be honest.
Comment 4 Matěj Cepl 2009-11-15 15:04:58 UTC 
Looks like a crash in Cairo. Reassigning.
Comment 5 Behdad Esfahbod 2009-11-16 18:14:26 UTC 
Assertion failure in xcb.  Lets reassign to xcb.  Let me know if cairo's calling xlib in a way it shouldn't do.
Comment 6 Adam Jackson 2009-11-24 16:01:20 UTC 
#7  0x00876bd8 in __assert_fail (assertion=<value optimized out>, 
    file=<value optimized out>, line=<value optimized out>, 
    function=<value optimized out>) at assert.c:81
        buf = 0xae939920 "firefox: xcb_io.c:378: _XAllocID: Assertion `ret != inval_id' failed.\n"

This is XCB's internal XID generation failing.  cairo's not doing anything wrong.
Comment 7 Matěj Cepl 2009-11-24 22:49:44 UTC 
*** Bug 541051 has been marked as a duplicate of this bug. ***
Comment 8 Yanko Kaneti 2009-11-24 23:59:47 UTC 
*** Bug 528388 has been marked as a duplicate of this bug. ***
Comment 9 Mads Kiilerich 2009-11-25 00:10:14 UTC 
XID? FWIW I had plenty of
  (npviewer.bin:2113): Gdk-WARNING **: XID collision, trouble ahead
in my .xsession-errors
Comment 10 Matěj Cepl 2009-11-25 16:22:18 UTC 
*** Bug 540136 has been marked as a duplicate of this bug. ***
Comment 11 Matěj Cepl 2009-12-10 00:00:03 UTC 
*** Bug 543763 has been marked as a duplicate of this bug. ***
Comment 12 Matěj Cepl 2009-12-10 00:00:03 UTC 
*** Bug 545230 has been marked as a duplicate of this bug. ***
Comment 13 Matěj Cepl 2009-12-10 00:00:03 UTC 
*** Bug 539341 has been marked as a duplicate of this bug. ***
Comment 14 Matěj Cepl 2009-12-10 16:17:14 UTC 
*** Bug 542838 has been marked as a duplicate of this bug. ***
Comment 15 Matěj Cepl 2009-12-10 16:17:15 UTC 
*** Bug 543074 has been marked as a duplicate of this bug. ***
Comment 16 Matěj Cepl 2009-12-10 16:17:15 UTC 
*** Bug 542739 has been marked as a duplicate of this bug. ***
Comment 17 Chris Campbell 2010-01-10 16:31:58 UTC 
*** Bug 554114 has been marked as a duplicate of this bug. ***
Comment 18 Chris Campbell 2010-03-12 01:30:41 UTC 
*** Bug 572345 has been marked as a duplicate of this bug. ***
Comment 19 Benjamin Otte 2010-10-14 16:12:48 UTC 
*** Bug 641959 has been marked as a duplicate of this bug. ***
Comment 20 Adam Jackson 2010-10-28 14:16:58 UTC 
Backtrace is from an old version of abrt that doesn't include enough information to know what version of Mesa is in use.
Comment 21 Mads Kiilerich 2010-10-28 14:23:22 UTC 
Removing abrt_hash:6597b3cdcdb717dcc084ae5772f41e15f8e6b569 so the next victim will file a new (and better?) backtrace.
Comment 22 Benjamin Otte 2010-11-16 19:09:12 UTC 
*** Bug 641959 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.