all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: stefan@marxist.se, 38187@debbugs.gnu.org
Subject: bug#38187: 27.0.50; No mouse-wheel scaling on images
Date: Thu, 21 Nov 2019 22:26:30 +0100	[thread overview]
Message-ID: <87blt4x6nt.fsf@gnus.org> (raw)
In-Reply-To: <87pnhmm9ui.fsf@mail.linkov.net> (Juri Linkov's message of "Thu,  21 Nov 2019 01:00:53 +0200")

Juri Linkov <juri@linkov.net> writes:

> BTW, while testing it for image scaling on a quite small image file,
> Emacs consumed several GB of all available memory and almost all swap,
> before I noticed and evaluated M-: (clear-image-cache) that freed memory.
>
> Memory leak?

No, it's just that Emacs' image cache is very primitive.  You can easily
get Emacs to go out-of-memory by just doing a

(dolist (file (directory-files dir-with-lots-of-images))
  (erase-buffer)
  (insert-image (create-image file)))

You get the same effect by altering the scaling factor, I think?  Each
scaled image is cached?  So by rolling the wheel ten clicks you get ten
cached copies of the image.

A better eviction algorithm would be nice.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2019-11-21 21:26 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 20:38 bug#38187: 27.0.50; No mouse-wheel scaling on images Juri Linkov
2019-11-14 12:48 ` Eli Zaretskii
2019-11-17 10:04   ` Lars Ingebrigtsen
2019-11-17 16:05     ` Eli Zaretskii
2019-11-17 16:07       ` Lars Ingebrigtsen
2019-11-17 21:20         ` Stefan Kangas
2019-11-17 22:42           ` Juri Linkov
2019-11-18  9:10             ` Lars Ingebrigtsen
2019-11-18 21:37               ` Juri Linkov
2019-11-19  3:31                 ` Eli Zaretskii
2019-11-20 23:00                   ` Juri Linkov
2019-11-21  3:35                     ` Eli Zaretskii
2019-11-21 21:18                     ` Alan Third
2019-11-21 22:51                       ` Juri Linkov
2019-11-22  7:47                         ` Eli Zaretskii
2019-11-21 21:26                     ` Lars Ingebrigtsen [this message]
2019-11-21 22:57                       ` Juri Linkov
2019-11-21 23:10                         ` Lars Ingebrigtsen
2019-11-22  7:58                           ` Eli Zaretskii
2019-11-22  7:51                         ` Eli Zaretskii
2019-11-22  7:31                       ` Eli Zaretskii
2019-11-22 12:41                         ` Lars Ingebrigtsen
2019-11-22  9:50                       ` Alan Third
2019-11-22 10:04                         ` Eli Zaretskii
2019-11-22 10:33                           ` Alan Third
2019-11-22 13:26                             ` Eli Zaretskii
2019-11-19  8:09                 ` Lars Ingebrigtsen
2019-11-20 23:12                   ` Juri Linkov
2019-11-21 12:11                     ` Lars Ingebrigtsen
2019-11-21 14:25                       ` Eli Zaretskii
2019-11-21 22:45                         ` Juri Linkov
2019-11-23 22:23                       ` Juri Linkov
2019-11-27 11:58                         ` Lars Ingebrigtsen
2019-11-17 23:01           ` Drew Adams
2019-11-18  9:08           ` Lars Ingebrigtsen
2019-11-19 14:49             ` Stefan Kangas
2019-11-19 15:27               ` Drew Adams
2019-11-19 16:07                 ` Stefan Kangas
2019-11-19 16:12                   ` Stefan Kangas
2019-11-19 16:27                   ` Drew Adams
2019-11-21  0:01                     ` Stefan Kangas
2019-11-21  0:41                       ` Drew Adams
2019-11-19 16:31                   ` Eli Zaretskii
2019-11-19 16:54                     ` Stefan Kangas
2019-11-19 22:50                       ` Juri Linkov
2019-11-19 17:27                   ` 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=87blt4x6nt.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=38187@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=stefan@marxist.se \
    /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.