Bug 83700 - vim becomes a runaway process
vim becomes a runaway process
Product: Red Hat Linux
Classification: Retired
Component: vim (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
David Lawrence
: 61141 78350 83177 88458 91629 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2003-02-07 01:25 EST by Danny Sung
Modified: 2007-04-18 12:50 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-21 10:42:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Danny Sung 2003-02-07 01:25:28 EST
I can consistently make vim become a runaway process by loading it in a window
and closing the window in which it was created.  This happens either locally or
remotely (either in a xterm/gnome-terminal or through a putty/ssh session). 
I've seen this for several versions of redhat (I think since 6.2, but I'm not
sure).  I'm using the latest version right now, 6.1-18.7x.2.  It only seems to
happen to the vim-enhanced version, however, and not vim-minimal.  Rebuilding
from the src.rpm produces the same affect.
Comment 1 Tim Tregubov 2003-05-22 12:50:30 EDT
I can do the same, in fact we have several general login servers which consistently get loaded up 
with runnaway vim and xemacs processes both of which seem to hang in the same consistent 
manner.    All you gotta do is ssh into a box, start vim, close your terminal without quitting vim...  

I've seen this on 7.2-9.0 machines...
Comment 2 Tim Tregubov 2003-05-22 13:01:07 EDT
never mind just found this on the vim page:

29.9. When I kill the xterm running Vim, the Vim process continues to run
      and takes up a lot of CPU (99%) time. Why is this happening?

When Vim is built with support for Python interface, you will have this
problem. This is a known problem with a python thread library and Vim.  To
solve this problem, use a Vim binary built without the Python interface.

For more information, read

    :help +python
    :help python

Doesn't look like there is a fix yet...

Comment 3 Karsten Hopp 2003-05-30 08:57:58 EDT
*** Bug 91629 has been marked as a duplicate of this bug. ***
Comment 4 Karsten Hopp 2003-06-20 07:49:04 EDT
*** Bug 88458 has been marked as a duplicate of this bug. ***
Comment 5 Karsten Hopp 2003-06-20 07:50:08 EDT
*** Bug 83177 has been marked as a duplicate of this bug. ***
Comment 6 Karsten Hopp 2003-06-20 07:51:43 EDT
*** Bug 78350 has been marked as a duplicate of this bug. ***
Comment 7 Karsten Hopp 2003-06-20 08:00:35 EDT
*** Bug 61141 has been marked as a duplicate of this bug. ***
Comment 8 John Hardin 2003-09-25 13:33:06 EDT
This is happening to us, too. 

dkl, can we get a fixed vim built and released? Or perhaps a fixed Python thread
library if vim +python is too useful to lose?


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