GNU bug report logs - #56546
29.0.50; unbounded RAM comsumption when displaying images

Previous Next

Full log

Message #29 received at 56546 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: mail <at> jao.io, 56546 <at> debbugs.gnu.org
Subject: Re: bug#56546: 29.0.50; unbounded RAM comsumption when displaying
 images
Date: Thu, 14 Jul 2022 12:15:03 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

> Don't we allocate memory for the cached stuff?  If so, we could count
> the bytes there, and record them in the cache itself.

No, we just call the gif/webp functions, and they allocate stuff on
their own.  For webp, we do know the size of the main data blob, but not
for GIF -- we just call DGifOpenFileName+DGifSlurp, and looking over the
documentation, there doesn't seem to be any way to get it to cough up
how much data it allocated.

In the non-file case, we know the size of the data blob, and I guess we
could just see how big the GIF file is in the DGifOpenFileName case, and
assume that it allocates memory for the entire file.  (Which may or may
not be true -- perhaps it uses mmap into the file instead, or
whatever...)

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.