Bug 104863

Summary: XEmacs 21.4.8 fails to terminate when X display lost
Product: [Retired] Red Hat Linux Reporter: Chris Hollowell <hollowec>
Component: xemacsAssignee: Jens Petersen <petersen>
Status: CLOSED CURRENTRELEASE QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
URL: http://list-archive.xemacs.org/xemacs-beta/200210/msg00410.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-09-25 08:03:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Supporting information from 21.4.10 patch none

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 
as CLOSE_WAIT.

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):
xemacs-21.4.8-16

How reproducible:
Always

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.