when vim catches a SIGHUP, it starts eating as much cpu as it can get and remains this way indefinately, until you kill -9 it.
verified..., I'm guessing this is a vim bug though.
xor: you should consider posting bugs with a different email address.
Basically this comes down to a weakness in Vim using all the various interpreters. (The Vim author will tell you it's a weakness in Linux since it works fine on BSD.) I suspect if you build Vim with USE="-perl -python -ruby" emerge vim then it will probably not exhibit the bug (though I haven't tried yet). Since lots of people use the embedded interpreters, I'm not going to change the default for the build. Aron