| Summary: | vi takes 100% CPU on terminal loss | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Vitaly Kushneriuk (RETIRED) <vitaly> |
| Component: | Current packages | Assignee: | Aron Griffis (RETIRED) <agriffis> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 1.0 RC6 r14 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Vitaly Kushneriuk (RETIRED)
2002-02-01 05:55:46 UTC
Reproduced locally, sent mail to vim-dev@vim.org. 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"
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? 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. 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 |