Bug 104863 - XEmacs 21.4.8 fails to terminate when X display lost
Summary: XEmacs 21.4.8 fails to terminate when X display lost
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xemacs
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Jay Turner
URL: http://list-archive.xemacs.org/xemacs...
Depends On:
TreeView+ depends on / blocked
Reported: 2003-09-22 21:26 UTC by Chris Hollowell
Modified: 2015-01-08 00:06 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2003-09-25 08:03:19 UTC

Attachments (Terms of Use)
Supporting information from 21.4.10 patch (1.89 KB, text/plain)
2003-09-22 21:29 UTC, Chris Hollowell
no flags Details

Description Chris Hollowell 2003-09-22 21:26:50 UTC
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):

How reproducible:

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
processing cycles.

Expected Results:  xemacs should terminate.

Additional info:

Comment 1 Chris Hollowell 2003-09-22 21:29:46 UTC
Created attachment 94643 [details]
Supporting information from 21.4.10 patch

Comment 2 Jens Petersen 2003-09-25 08:03:19 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.