unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: "corrupted size vs. prev_size"
Date: Tue, 12 Apr 2022 13:41:02 +0200	[thread overview]
Message-ID: <87ee22wmup.fsf@gnus.org> (raw)
In-Reply-To: <87mtgqworp.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 12 Apr 2022 12:59:38 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> After the recent GIF/WebP caching changes, I sometimes get "corrupted
> size vs. prev_size" and Emacs then hangs, so I guess I'm messing up
> something in the memory allocation/freeing/writing bits somewhere.

After doing more testing, the problem is definitely related to the
gif_load code, not the webp_load code.

And it only seems to trigger when there's errors in the GIF files (i.e.,
DGifSlurp etc reports that one of the GIFs can't be parsed).  So the
problem is either in the error handling on my side, or it could even be
a bug in the giflib library.  As previously reported, the version of
giflib that's in Debian/bookworm has problems parsing GIFs that earlier
or later versions of giflib doesn't have...

Hm.

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



  parent reply	other threads:[~2022-04-12 11:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 10:59 "corrupted size vs. prev_size" Lars Ingebrigtsen
2022-04-12 11:14 ` Andreas Schwab
2022-04-12 11:23   ` Lars Ingebrigtsen
2022-04-12 11:26     ` Po Lu
2022-04-12 11:41 ` Lars Ingebrigtsen [this message]
2022-04-12 11:45   ` Lars Ingebrigtsen
2022-04-12 12:26     ` Lars Ingebrigtsen
2022-04-12 12:54       ` Lars Ingebrigtsen
2022-04-12 13:13         ` Lars Ingebrigtsen
2022-04-12 14:09           ` Lars Ingebrigtsen
2022-04-12 11:44 ` 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

  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=87ee22wmup.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@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 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).