Bug 568978

Summary: [abrt] crash in firefox-3.5.8-1.fc12: Process /usr/lib/firefox-3.5.8/firefox was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Richard Jolly <richard.jolly>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: azevedo.davy, bugzilla, campbecg, gecko-bugs-nobody, msdeleonpeque, netsanction
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:3c3ebabd7db3025023b1e84c97df4c7638367103
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-03 20:43:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
Rpm Output as requested none

Description Richard Jolly 2010-02-27 10:28:57 UTC
abrt 1.0.7 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.5.8/firefox
component: firefox
executable: /usr/lib/firefox-3.5.8/firefox
kernel: 2.6.31.12-174.2.19.fc12.i686.PAE
package: firefox-3.5.8-1.fc12
rating: 4
reason: Process /usr/lib/firefox-3.5.8/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Richard Jolly 2010-02-27 10:29:02 UTC
Created attachment 396737 [details]
File: backtrace

Comment 2 Chris Campbell 2010-02-28 16:59:15 UTC
#7  0x007d6be8 in __assert_fail (assertion=<value optimized out>, 
    file=<value optimized out>, line=<value optimized out>, 
    function=<value optimized out>) at assert.c:81
        buf = 
    0x98e28f60 "firefox: xcb_io.c:378: _XAllocID: Assertion `ret != inval_id' failed.\n"
#8  0x00b67c0a in _XAllocID (dpy=0xb7560000) at xcb_io.c:378
        ret = 4294967295
        __PRETTY_FUNCTION__ = "_XAllocID"
#9  0x00dbdc48 in XRenderCreatePicture (dpy=<value optimized out>, 
    drawable=<value optimized out>, format=<value optimized out>, 
    valuemask=<value optimized out>, attributes=<value optimized out>)
    at Picture.c:90
        info = 0xb7589850
        pid = <value optimized out>
#10 0x046fef7a in _cairo_xlib_surface_ensure_dst_picture (surface=0x99061d30)
    at cairo-xlib-surface.c:887
No locals.




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Chris Campbell 2010-02-28 17:01:56 UTC
Reporter, if you are able, can you post steps we can use to reproduce this crash?

Also, if you are willing,

Thank you for taking the time to submit this bug report.

We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

First of all, could we get output of the command, saved in a text file and attached to this bug:

 $ rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin*

Please also install firefox-debuginfo.

 # debuginfo-install firefox

Then run firefox inside the gdb debugger. Please do the following:

 $ firefox -g

Stuff will appear. Ignore this until you get the gdb command prompt, then do:

 (gdb) run

Now, firefox should start up. Use it and reproduce the crash. When firefox crashes, you should be back to the gdb prompt. Now do:

 (gdb) thread apply all back-trace

More screens of stuff will occur. Copy all of this part to your editor of choice, such as gedit, and save it as an uncompressed file and attach it to this bug report.

We will review this issue again once you've had a chance to attach this information.




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Richard Jolly 2010-03-03 00:07:12 UTC
Created attachment 397446 [details]
Rpm Output as requested

Comment 5 Richard Jolly 2010-03-03 00:09:22 UTC
Cannot recall specifically the steps I went through to create this crash - but thank you for the instructions on the debug install and gdb debugger. If it occurs again I will follow the gdb instructions and send in the backtrace

Comment 6 Chris Campbell 2010-03-03 20:43:29 UTC
You're welcome. I am going to set this closed. Please feel free to reopen if you are able to reproduce this crash.