Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 471 - vi takes 100% CPU on terminal loss
Summary: vi takes 100% CPU on terminal loss
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Aron Griffis (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-01 05:55 UTC by Vitaly Kushneriuk (RETIRED)
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vitaly Kushneriuk (RETIRED) gentoo-dev 2002-02-01 05:55:46 UTC
gvim/vim sometimes eat up 100% when they lose terminal, like when you kill your
ssh session etc.
Comment 1 Aron Griffis (RETIRED) gentoo-dev 2002-02-01 12:22:20 UTC
Reproduced locally, sent mail to vim-dev@vim.org.  
Comment 2 Aron Griffis (RETIRED) gentoo-dev 2002-02-02 10:53:19 UTC
This bug only manifests itself when the python interpreter is compiled into Vim.
 I'm continuing to investigate, but a short-term solution is to edit the ebuild
so that python isn't compiled into Vim:

134c134
< 	use python && myconf="$myconf --enable-pythoninterp"
---
> #	use python && myconf="$myconf --enable-pythoninterp"
Comment 3 Daniel Robbins (RETIRED) gentoo-dev 2002-02-03 01:18:26 UTC
do you think it would hurt to disable the python interpreter (with a note in the
ebuild as to why) until this problem is fixed by the vim people?
Comment 4 Vitaly Kushneriuk (RETIRED) gentoo-dev 2002-02-03 04:56:55 UTC
I thinks it's better to leave python in, as this is not critical bug.
I personaly use vi's python scripting(started to study it) and 
find it a very neat feature. I also guess the issue will be resolved soon
by vi devs.
Comment 5 Aron Griffis (RETIRED) gentoo-dev 2002-02-16 10:46:08 UTC
The Vim developers are aware of the problem.  It can occur with any of the
interpreters (e.g. Python or Perl) that use threads.  There is no known remedy
at this time, since the problem is not specifically in Vim or the interpreters,
it's a conflict between using signals (in Vim) and threads (in the
interpreters).  Actually, the problem could be tracked to Linux or glibc, since
it doesn't occur on FreeBSD.

Since it's possible to omit the interpreters via USE, I'm going to leave the
ebuild as is.  It's not a killer bug since it doesn't crash the system.

Aron