unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: 33560@debbugs.gnu.org
Subject: bug#33560: closed (Re: bug#33560: 27.0.50; 6.4 GB of RAM)
Date: Wed, 05 Dec 2018 16:17:18 +0200	[thread overview]
Message-ID: <83efaw83dd.fsf@gnu.org> (raw)
In-Reply-To: <87d0qgdr6t.fsf@mat.ucm.es> (message from Uwe Brauer on Wed, 05 Dec 2018 14:43:54 +0100)

> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Wed, 05 Dec 2018 14:43:54 +0100
> 
>    > It's a bug in ImageMagick, an external library Emacs/Gnus uses to
>    > display djvu files. I suggest to take the problem up with
>    > ImageMagick developers, perhaps they know how to solve it or work
>    > around it.
> 
> The point is that gnus does not display any attachment, just presents a
> button (so that I can download the attachment if I wish). That is why I
> doubt that ImageMagick is responsible.

I think Gnus does invoke ImageMagick, even if it doesn't display the
image, as part of creating the button.  You can see if that is true
by attaching the debugger to Emacs while it is growing its memory
footprint: if I'm right, you will see some ImageMagick function(s) on
the callstack.

> It would be good, if one of the gnus developer would comment on this
> issue.

Agreed.





  reply	other threads:[~2018-12-05 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01  8:54 bug#33560: 27.0.50; 6.4 GB of RAM Uwe Brauer
2018-12-02  1:25 ` Glenn Morris
2018-12-05 13:45   ` Uwe Brauer
2018-12-05 13:49   ` Uwe Brauer
     [not found] ` <handler.33560.D33560.154371393329708.notifdone@debbugs.gnu.org>
2018-12-05 11:54   ` bug#33560: closed (Re: bug#33560: 27.0.50; 6.4 GB of RAM) Uwe Brauer
     [not found]   ` <87k1kodw8h.fsf@mat.ucm.es>
2018-12-05 12:26     ` Eli Zaretskii
2018-12-05 13:43       ` Uwe Brauer
2018-12-05 14:17         ` Eli Zaretskii [this message]
2018-12-05 17:37           ` Glenn Morris
2018-12-05 18:04             ` Eli Zaretskii
2018-12-05 17:19     ` Glenn Morris
2018-12-05 17:57       ` Uwe Brauer

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83efaw83dd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33560@debbugs.gnu.org \
    --cc=oub@mat.ucm.es \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).