raveling@venera.isi.edu (Paul Raveling) (06/02/89)
We have a few people using X11R3 on Sun 4's who've had a problem involving emacs (version 18.51). We've found a bypass, but if anyone can shed more light on the real problem we'd appreciate it. The problem is that the emacs client process and the X11 display server go compute-bound, apparently exchanging messages, when using $DISPLAY = "unix:0.0". All's well when $DISPLAY is "hostname:0.0". Also, the problem doesn't exist on a presumably compatible Solbourne. This alone suggests a problem in the OS (SunOS Release Sys4-3.2_REV2), but it's still not clear. It appears that all's well until the emacs client gets some form of expose event; circumstantial evidence suggests perhaps a GraphicsExpose starts it. Once started, both emacs and the display server stay busy until the emacs client process is killed. This suggests the problem might be in some aspect of mutual interaction among the OS, the display server, and the emacs client. Has anyone else seen this and investigated it? ---------------- Paul Raveling Raveling@isi.edu