bug#38345: 27.0.50; Permanent increase in memory consumption after opening images (or pdfs)

[Eli Zaretskii]

> From: Ihor Radchenko <yantar92@gmail.com>
> Cc: 38345@debbugs.gnu.org
> Date: Sun, 24 Nov 2019 00:04:17 +0800
> 
> Hmm. Following an article by Dima Kogan [1], it appears to me that free()
> should de-allocate memory in the program's address space (or at least
> memory drop should be visible in the plot I got, since I used the same
> memory debugging tools)

It may be useful to try memory mapping tools that show which part(s)
of a program "own" specific regions of memory.  It could be that the
memory growth is due to some library Emacs uses to show images, for
example.  Those tools usually also show the memory in the free pool of
the program's address space, so you should be able to see what's going
on when you call clear-image-cache.