From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: 61763@debbugs.gnu.org
Subject: bug#61763: 30.0.50; Image Cache Size growth
Date: Fri, 24 Feb 2023 22:43:10 +0200 [thread overview]
Message-ID: <837cw6n6ap.fsf@gnu.org> (raw)
In-Reply-To: <878rgmlsg2.fsf@ledu-giraud.fr> (message from Manuel Giraud on Fri, 24 Feb 2023 21:27:41 +0100)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: 61763@debbugs.gnu.org
> Date: Fri, 24 Feb 2023 21:27:41 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> [...]
>
> >> Can you reproduce (if you have time)?
> >
> > Not sure what I need to reproduce. I've visited 6 images of 2 MiB
> > each and Memory Report says I have 581 MiB in my image cache.
> > Meanwhile the memory footprint of the Emacs process is 350 MiB. Is
> > this what you wanted to see?
>
> Ok. So in the same ballpark. I thought there was something wrong on my
> setup.
>
> Why I think this growth is wrong is because it seems high. And if I'm
> browsing some images in Emacs, I'm getting a "Memory exhausted (restart
> Emacs)" message after only 20 or 30 images.
JPEG compression is very good, it routinely compresses images with
ratios of 10:1 to 20:1. If I use djpeg to convert the 2 MiB images I
used into BMP, I get 36 MiB BMP files -- that's a 1:18 expansion
ratio. And Emacs converts each image to a pixmap for display, which
is basically similar to what I did. Multiply that by 20 or 30, and
you get the numbers you see, I think.
The solution is to enlarge the VM for your machine (by enlarging swap,
for example). If you don't keep those images displayed in windows,
lowering image-cache-eviction-delay might also help.
next prev parent reply other threads:[~2023-02-24 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 17:00 bug#61763: 30.0.50; Image Cache Size growth Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-24 17:12 ` Eli Zaretskii
2023-02-24 19:41 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-24 19:55 ` Eli Zaretskii
2023-02-24 20:27 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-24 20:43 ` Eli Zaretskii [this message]
2023-02-24 21:32 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-25 7:09 ` Eli Zaretskii
2023-02-25 12:19 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-25 13:24 ` Eli Zaretskii
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=837cw6n6ap.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61763@debbugs.gnu.org \
--cc=manuel@ledu-giraud.fr \
/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).