From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Jose A. Ortega Ruiz" <mail@jao.io>
Cc: 56546@debbugs.gnu.org
Subject: bug#56546: 29.0.50; unbounded RAM comsumption when displaying images
Date: Sat, 16 Jul 2022 12:37:58 +0200 [thread overview]
Message-ID: <87y1wts5q1.fsf@gnus.org> (raw)
In-Reply-To: <87r12mhrjb.fsf@mail.jao.io> (Jose A. Ortega Ruiz's message of "Sat, 16 Jul 2022 00:42:16 +0100")
"Jose A. Ortega Ruiz" <mail@jao.io> writes:
> I was also naively expecting
> that, given that i'm reloading the same page with the "same" images,
> they'd be found in the cache the second and subsequent times, but, since
> the cache size increases, i see that they're not considered the "same"
> by the caching mechanism; i can again see reasons for that behaviour (i
> am sure the cache is not judging image equality using "image urls"),
> just mentioning it in case it's unexpected or there's an easy way of
> reusing the cached images).
From Emacs' point of view, these aren't "the same", because they're
not taken (directly) from files, I think.
> Anyway, thanks a lot for bearing with me and solving the problem: this
> bug is all but fixed now from my point of view.
Thanks for checking; I'm closing this bug report, then.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-07-16 10:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 1:35 bug#56546: 29.0.50; unbounded RAM comsumption when displaying images Jose A. Ortega Ruiz
2022-07-14 5:45 ` Eli Zaretskii
2022-07-14 6:04 ` Eli Zaretskii
2022-07-14 8:53 ` Lars Ingebrigtsen
2022-07-14 9:15 ` Eli Zaretskii
2022-07-14 9:20 ` Lars Ingebrigtsen
2022-07-14 10:01 ` Lars Ingebrigtsen
2022-07-14 10:10 ` Eli Zaretskii
2022-07-14 10:15 ` Lars Ingebrigtsen
2022-07-14 12:23 ` Jose A. Ortega Ruiz
2022-07-14 16:59 ` Lars Ingebrigtsen
2022-07-14 17:26 ` Eli Zaretskii
2022-07-14 17:51 ` Glenn Morris
2022-07-14 18:08 ` Lars Ingebrigtsen
2022-07-15 23:42 ` Jose A. Ortega Ruiz
2022-07-16 10:37 ` Lars Ingebrigtsen [this message]
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=87y1wts5q1.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=56546@debbugs.gnu.org \
--cc=mail@jao.io \
/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).