Bug 548895

Summary: Assertion failure in _XAllocID inside XRenderCreatePicture running /usr/share/abrt/CCMainWindow.py
Product: [Fedora] Fedora Reporter: Dzmitry <dkanunnikau>
Component: abrtAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: anton, dfediuck, dmalcolm, dvlasenk, iprikryl, ivazqueznet, james.antill, jeremy.butler36, jmoskovc, jonathansteffan, kklic, mnowak, npajkovs
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:0c4a9c9cd1d0ce27c0b4ca2a5ab13ab92d8d3ef5
Fixed In Version: abrt-1.0.7-1.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-23 05:38:49 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

Description Dzmitry 2009-12-19 08:55:17 UTC 
abrt 1.0.0 detected a crash.

Attached file: backtrace
cmdline: /usr/bin/python /usr/share/abrt/CCMainWindow.py
component: python
executable: /usr/bin/python
kernel: 2.6.31.6-166.fc12.i686.PAE
package: python-2.6.2-2.fc12
rating: 4
reason: Process was terminated by signal 6
Comment 1 Dzmitry 2009-12-19 08:56:07 UTC 
Created attachment 379321 [details]
File: backtrace
Comment 2 Dave Malcolm 2009-12-21 19:20:28 UTC 
Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What version of abrt-gui do you have installed?

Looking at the backtrace, it looks like an assertion failed inside frame 3 of the program's single thread inside _XAllocID.

Reassigning component from "python" to "abrt"
Comment 3 Dzmitry 2009-12-21 19:52:54 UTC 
abrt-1.0.0-1.fc12.i686

i think it happened when abrt was preparing an enormous report for that yumex crash. i have not tried to reproduce the problem again
Comment 4 Dave Malcolm 2009-12-21 19:58:34 UTC 
(In reply to comment #3)
> abrt-1.0.0-1.fc12.i686
> 
> i think it happened when abrt was preparing an enormous report for that yumex
> crash. i have not tried to reproduce the problem again  

Thanks for the info!

For reference, the yumex crash referred to is bug 548849, which has a backtrace with almost 200000 frames.  I suspect that the sheer size of this backtrace is responsible for some ABRT crashes (it caused one of my scripts to melt down...)
Comment 5 Denys Vlasenko 2010-02-09 03:08:41 UTC 
"sheer size of the backtrace" problem is dealt with in git. We use several measures to make sure backtrace text is < 256k.
Setting to MODIFIED.
Comment 6 Jiri Moskovcak 2010-02-10 09:44:13 UTC 
The report dialog uses TextView to show the backtrace since abrt 1.0.4, so it should be able to handle large texts much better.

J.
Comment 7 Fedora Update System 2010-02-15 14:07:14 UTC 
abrt-1.0.7-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/abrt-1.0.7-1.fc12
Comment 8 Fedora Update System 2010-02-18 22:31:07 UTC 
abrt-1.0.7-1.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update abrt'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1598
Comment 9 Fedora Update System 2010-02-23 05:37:10 UTC 
abrt-1.0.7-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.