From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33275@debbugs.gnu.org
Subject: bug#33275: 27.0.50; Image cache pruning
Date: Mon, 05 Nov 2018 20:13:27 +0100 [thread overview]
Message-ID: <m3bm73gwx4.fsf@gnus.org> (raw)
In-Reply-To: <83k1lrcqza.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 05 Nov 2018 20:35:21 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> We still could use the memory limit calculated by get_lim_data in
> strategic places, like cache_image, to catch situations where the
> cache size exceeds some fraction of what ret_lim_data returns. Would
> that work?
If I understand you correctly, you seem to favour introducing code that
will break code that's working today (if you insert an image into a
buffer today in a memory-pressure situation, that won't signal an error
today) instead of tweaking a non-documented ad-hoc caching strategy (by
taking the image cache size into consideration), or fixing the caching
(by using weak hash tables), and I'm not quite sure why.
`image-size' didn't use to cache images, but was introduced as an
optimisation.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-11-05 19:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 14:07 bug#33275: 27.0.50; Image cache pruning Lars Ingebrigtsen
2018-11-05 16:05 ` Eli Zaretskii
2018-11-05 16:18 ` Lars Ingebrigtsen
2018-11-05 16:23 ` Eli Zaretskii
2018-11-05 16:35 ` Lars Ingebrigtsen
2018-11-05 17:27 ` Eli Zaretskii
2018-11-05 17:36 ` Lars Ingebrigtsen
2018-11-05 17:48 ` Lars Ingebrigtsen
2018-11-05 18:14 ` Eli Zaretskii
2018-11-05 18:35 ` Eli Zaretskii
2018-11-05 19:13 ` Lars Ingebrigtsen [this message]
2018-11-05 19:28 ` Eli Zaretskii
2018-11-09 12:22 ` Lars Ingebrigtsen
2018-11-06 15:40 ` Eli Zaretskii
2018-11-09 12:26 ` Lars Ingebrigtsen
2018-11-10 9:48 ` Eli Zaretskii
2019-09-21 8:18 ` Lars Ingebrigtsen
2018-11-05 18:18 ` Eli Zaretskii
2018-11-05 19:06 ` Lars Ingebrigtsen
2018-11-05 19: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bm73gwx4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=33275@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.