From Bugzilla Helper:
Description of problem:
XEmacs fails to terminate when the connection to the X display is
lost. Furthermore, when this occurs, XEmacs begins consuming
an exorbitant amount of processing cycles. An lsof run on the
system indicates the TCP state of the the process' X connection
According to an entry on the XEmacs mailing list (see provided URL),
this bug has been fixed in 21.4.10. After compiling/installing
21.4.14, I've verified that this problem is not present in that revision.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use ssh login to a remote system (enable X11 Forwarding)
2. Execute 'xemacs somefile &'
3. Send SIGKILL to the ssh client
Actual Results: xemacs on the remote machine was still running, and consuming
Expected Results: xemacs should terminate.
Created attachment 94643 [details]
Supporting information from 21.4.10 patch
I suggest upgrading to a newer version of XEmacs then.
While this sounds pretty annoying, I'm sorry but I don't feel
this is serious enough to warrant an errata.