Crashing the window mgr from GL programs

[Stuart Levy]

We use a locally-written 3-d object viewer on our Irises (personal and GTX).
For some aberrant objects, or possibly some xform matrices pushed on the stack,
we find it causes the window server to crash -- with messages resembling
"timeout: graphics FIFO still > 1/2 full" and/or "window server killed with
signal 15".  In extreme cases it can cause our GTX Iris to lock up such that
we must reboot to recover the graphic display, though normally we're just
kicked back to a login: prompt.

Does anyone know what kinds of geometric data can wedge the graphics subsystem
this way?  If we knew what to avoid we might be able to change our application
to prevent crashes.

	Stuart Levy, Geometry Group, University of Minnesota
	slevy at geom.umn.edu