Red Hat Bugzilla – Bug 188126
X segfaults on scaled images in seamonkey (cairo-gtk2)
Last modified: 2007-11-30 17:11:29 EST
Description of problem:
X crashed when I opened the large feed of
http://wp.netscape.com/fishcam/fishcam.html in a cairo-gtk2 test build of
seamonkey. The bug didn't show when I tried to reproduce it.
Version-Release number of selected component (if applicable):
Not (yet) reproduced
Steps to Reproduce:
1. Browse around with cairo-gtk2 enabled mozilla.
2. Go to URL
3. Open Large Feed
X may crash
Xorg.0.log.old had this backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x87) [0x80b86c7]
2: /usr/lib/xorg/modules/libfb.so [0x2715d1]
3: /usr/lib/xorg/modules/libfb.so [0x27784e]
4: /usr/lib/xorg/modules/libfb.so(fbCompositeGeneral+0x855) [0x275505]
5: /usr/lib/xorg/modules/libfb.so(fbComposite+0x1cd) [0x27fdbd]
6: /usr/lib/xorg/modules/libxaa.so(XAAComposite+0x261) [0x2d5261]
7: /usr/bin/Xorg [0x81543e6]
8: /usr/bin/Xorg(CompositePicture+0xf7) [0x8142007]
9: /usr/bin/Xorg [0x8147d6c]
10: /usr/bin/Xorg [0x81450a5]
11: /usr/bin/Xorg(Dispatch+0x19b) [0x80888eb]
12: /usr/bin/Xorg(main+0x487) [0x80701d7]
13: /lib/libc.so.6(__libc_start_main+0xdc) [0x1167e4]
14: /usr/bin/Xorg(FontFileCompleteXLFD+0xb1) [0x806f511]
Fatal server error:
Caught signal 11. Server aborting
Will installing xorg-x11-server-debuginfo help create a more useful backtrace
when/if it happens again?
Created attachment 127401 [details]
xorg log with backtrace
It did happen again today - so it's rather hard to reproduce.
It's caused by https://bugzilla.mozilla.org/show_bug.cgi?id=334951 and as
comment 9 there says, the browser seems to load random video memory sometimes.
That's obviously bad behaviour, but I don't think it should be able to crash X.
I've not been able to load the fishcam image for some time, but images resized
to fit the browser window do often show the broken behaviour. For example:
This has apparently been fixed by the xorg team. (See external bug reference)
So this should be fixed in FC6, I guess.
This bug's also discussed in https://bugzilla.novell.com/show_bug.cgi?id=152730
Per comment #4 and the upstream bug, this should be fixed in FC6. Please reopen
if this issue reoccurs for you.