Mathias Michaelis wrote:
Dear developers
I observe the following strange behaviour of gvim 7.0 on Windows XP
built with HUGE features by my own:
I open gvim.exe, work with it or leave it without touching it for
half an hour. Then, within gvim.exe, I type ":q" or ":wq". gvim
saves the text, remove the .swp file and closes its window -- all as
expected. But if I invoke the Taskmanager by pressing
Ctrl-Alt_Delete, then I observe a gvim zombie hanging around within
the task list.
I have tried all to make this phenomena more reproducible, but
nothing helps: You may open and close gvim hundred times, or may
open and close with gvim a hundred files, you may do heavy work with
it or can leave it alone, all that does not matter. The only thing
that matters is the time you keep gvim open: On my (old) machine,
gvim closes properly if I quit it after five minutes, but if I quit
it only after 30 minutes, it keeps hanging around in the task list.
There is a second parameter that matters: The features you include
into your built of gvim. Alas, I could not yet found clearly, which
features this strange behaviour depends on.
Has anybody similar effects? Or do I do something wrong? See below
how I built my version of gvim.
Thanks very much for any help, hints, proposals or anything that
could help to trace down this effect.
With kind regards
Mathias
If it doesn't happen when you build with Big features (and an otherwise
identical configuration), then the only difference between Big and Hige
is that the latter has +profile
Best regards,
Tony.
