Comment 5 for bug 279240
Revision history for this message
| Ariel Faigon (ariel.faigon) wrote Re: firefox dies mentioning RenderBadPicture and a failed assertion | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Just want to confirm I see this too very often.
Firefox 3.x used to be stable as a rock (no crashes for weeks) under Hardy with KDE 3.5
After upgrading to Intrepid (KDE4, new QT, new Xorg) it started crashing every hour or so with SEGV after the X assertion failure. Here's how a session looks like when I start firefox from a shell:
<code>
$ /usr/bin/firefox
(firefox:30311): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at
session startup.
(firefox:30311): atk-bridge-WARNING **: IOR not set.
(firefox:30311): atk-bridge-WARNING **: Could not locate registry
[Note: the above messages appear at startup, and are probably unrelated.
then firefox works fine for a while and finally crashes with this:]
QPixmap: Invalid pixmap parameters
The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 955915 error_code 169 request_code 152 minor_code 7)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
Segmentation fault
52.779u 3.292s 25:38.58 3.6% 0Kshar+
</code>