Re: #127986: vim: Processes found running away. * Tags: moreinfo; 158 days old.
> Why would you be running killall gvim?
It happens to me in practice when I start a screen session at home, then
connect to it from work and inadvertently start gvim on the home X
server. A subsequent attempt to edit the same file in vim produces the
standard "swap file exists" warning, prompting a "killall gvim".
So this is admittedly caused by a case of PEBKAC, but the bug is real.
gvim should not busyloop when it receives SIGTERM.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com