bjbarcla / mrxvt

Automatically exported from code.google.com/p/mrxvt
0 stars 1 forks source link

Kill'ed mrxvt Leaves Orphaned Processes Behind #6

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Open mrxvt.
2. Launch process in one or more tabs (top, mutt, etc, even with a newly
launched mrxvt session with just one tab, the bash shell).
3. Kill the mrxvt window (using xkill, "xkill - kill a client by its X
resource," for example).

What is the expected output? What do you see instead?
I expect all mrxvt child processes and mrxvt to be kill'ed, but instead,
mrxvt alone dies, orphaning any and all child processes, so that all the
bash shells and processes running within these shells that were launched by
mrxvt stay running indefinitely, with a parent process id (ppid) of 1
rather than mrxvt's ppid.  As an added bonus :(, these orphaned processes
won't go down completely without a kill -9.

What version of the product are you using? On what operating system?
Can be replicated with latest Unstable and Stable versions
(http://code.google.com/p/mrxvt/wiki/Download), 0.5.4 and 0.4.2, along with
the latest development version from the subversion repository, "Revision:
404."  This was tested on year old versions of Debian and Ubuntu.

Please provide any additional information below.
* Each mrxvt install from above was configured using the following
configure statement:
./configure --prefix=/usr/local --disable-xrender --enable-menubar
--enable-mouseslipwheel --enable-text-shadow --enable-xft --with-max-term=128
* The above occurs even no mrxvt configuration in place (that includes
~/.Xdefaults).
* The -hold option, whether using [-/+]hold on the latest stable mrxvt
version or -hold 0x00 on the newer unstable versions, didn't help.
* It seems that I'm not the first to run into this issue, though in most of
these examples, the issue occurs with zsh rather than bash:
http://www.mail-archive.com/misc@openbsd.org/msg61002.html
http://mailman.linuxchix.org/pipermail/techtalk/2009-May/023666.html
http://www.zsh.org/mla/users/2007/msg00019.html

Original issue reported on code.google.com by Sub.x...@gmail.com on 28 Apr 2010 at 9:29

GoogleCodeExporter commented 8 years ago
FYI: This appears to be caused by/a duplicate of issue 8 (the "extra PTY" 
problem).  Without the errant PTY, processes don't hang around after the xkill.

Original comment by tyson.tu...@gmail.com on 28 Mar 2012 at 3:31