Description of problem: Attached postscript file crashes X server.
Created attachment 114087 [details] broken.ps.gz
Hi William, Can you provide more details to what you mean by "crash"? Does it bring you back to the GDM login screen? Or does it freeze up hard? If it freezes up can you still move your mouse? Also, what versions of xorg-x11 and ggv do you have installed? Thanks.
On RHEL4 it freezes up hard and I can't move the mouse. On FC3 it brings me back to GDM. RHEL4: xorg-x11-6.8.1-23.EL FC3: xorg-x11-6.8.2-1.FC3.13 FYI, I also reported this to evince upstream. http://bugzilla.gnome.org/show_bug.cgi?id=303264 I'm setting up a workstation where I can test this a bit more.
*** Bug 157079 has been marked as a duplicate of this bug. ***
I'm going to assign this bug to the xorg team. X shouldn't be crashing when an app does something abnormal. Also, some of the xorg team have done extensive development work on evince and so are more qualified than me to look at this problem.
Actually, on RHEL4 it only appears to freeze up hard sometimes. The video state gets corrupted somehow even when switching VTs. Sometimes X dies and GDM restarts and things seems normal.
If this issue is still occuring in the latest Red Hat Enterprise Linux 4 updates, please contact Red Hat Support Services and file an official support ticket by visiting http://www.redhat.com/support or by calling 1-888-RED-HAT1 depending on the type of support contract.
Reporter, can you still reproduce this bug with updated RHEL4? The Xorg shouldn't crash now. However, note that Xorg is asked to create for ggv REALLY huge bitmap (around 1.5GB according to upstream bug) so if you have less memory you can your computer into state which looks like frozen (and for all your purposes it is -- you cannot even move a mouse), but unfortunately it is just a characteristic of the current single-threaded X server which waits until this request is completed. There used to be a bug in X server which crashed when asking for allocation of extremely large pixmaps, but that should be fixed (everywhere including RHEL4). Regretting it but I have to close this as CANTFIX (because it was already fixed). Reopen with additional information if you have any.