Re: gnus: apparently kills external viewers too aggressively

[David Coe <davidc@debian.org>]

Simon Josefsson <jas@extundo.com> writes:

> Makes sense, the patch below has been installed.  It tries to
> interrupt the process in a loop with a echo area message, and when it
> is dead, or you press C-g, it goes on and send it a final KILL and
> remove the files.

Thanks.  That works nicely, but the message "Waiting for external
displayer to die..." doesn't go away (until user does something, like
select the next message).  The external display process does get
stopped correctly (and it does destroy the shared segments it had
allocated), but the message implies to the user that gnus is still
waiting.

Is there a better way to deal with that message, or do we have a bug
somewhere else? (Perhaps I or debian gnus/emacs have something wrong.)

> Still, display seem to leave some memory around.  Starting display
> allocates some buffers:
[...]

> Killing display cleanly removes some buffers, but not all:
[...]

That doesn't happen here; maybe that other segment is created by
something else?  'ipcs -p' will show you the creator (and last
accessor) processes; not important, unless you're interested.

Thanks again.