From: Manoj Srivastava <srivasta@debian.org>
Cc: David Coe <davidc@debian.org>, 200823-forwarded@bugs.debian.org
Subject: gnus: apparently kills external viewers too aggressively
Date: Wed, 20 Aug 2003 13:17:40 -0500 [thread overview]
Message-ID: <87vfss42ij.fsf@glaurung.green-gryphon.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
Gnus v5.10.2
GNU Emacs 21.3.2 (i386-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2003-04-24 on raven, modified by Debian
200 news.vmware.com InterNetNews NNRP server INN 1.7.2 08-Dec-1997 ready (posting ok).
Hi,
[Please retain the CC to 200823-forwarded@bugs.debian.org in
your response, so that the Debian bug tracking system as a
record of your input]
This bug was reported by a Debian user
In gnus under 'emacs -nw' running in an xterm, to view an image/jpeg
MIME attacment, gnus launches 'display XXXX.jpeg' which opens up an
imagemagick window containing the image.
If I close that imagemagick window directly, there's no problem; but
if I let gnus close it (by, e.g., hitting ENTER again on the
image/jpeg line in the mail message, or by hitting 'n' to go to the
next message, or 'q' to leave the current group) gnus apparently kills
the imagemagick ('display') process too aggressively, causing it to
leave two shared memory segments allocated.
Do this enough times and you eventually run out of swap space. Even
after gnus and emacs and X have been successfully stopped, the shared
memory segments are still there ('ipcs -m' shows them; 'ipcrm -m ...'
successfully removes them).
Maybe this is a bug in imagemagick, but I suspect gnus is sending it
SIGKILL instead of SIGTERM, or something to that effect. I have not
looked at the source code.
Let me know if you need more info, or if I can help in any way.
Thanks.
[-- Attachment #2: User settings --]
[-- Type: application/emacs-lisp, Size: 19061 bytes --]
[-- Attachment #3: Type: text/plain, Size: 405 bytes --]
--
A brahmin is called so by breaking with evil deeds. It is by pious
behaviour that a man is called a man of religion, and by casting out
blemishes one is called one gone forth. 388
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
next reply other threads:[~2003-08-20 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 18:17 Manoj Srivastava [this message]
2003-08-20 23:25 ` Simon Josefsson
2003-08-26 17:58 ` David Coe
2003-08-27 1:47 ` Simon Josefsson
2003-08-27 4:55 ` David Coe
2003-08-27 6:03 ` Simon Josefsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vfss42ij.fsf@glaurung.green-gryphon.com \
--to=srivasta@debian.org \
--cc=200823-forwarded@bugs.debian.org \
--cc=davidc@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).