From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23431@debbugs.gnu.org, jch@pps.univ-paris-diderot.fr
Subject: bug#23431: 25.0.93; EWW hangs
Date: Tue, 03 May 2016 21:37:42 +0200 [thread overview]
Message-ID: <87vb2v0w6x.fsf@gnus.org> (raw)
In-Reply-To: <83mvo7j5vg.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 03 May 2016 22:31:15 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Btw, if I wait for a while (maybe 20 sec), the slowness disappears,
> and Emacs becomes responsive again, although the animation still goes
> on. So perhaps what causes this is some initial processing? (I have
> no idea what's involved in displaying an animated GIF.)
After Emacs has decoded all the frames in the image, they'll then be
stored in the Emacs display image cache (the one you can clear with
`clear-image-cache'), so Emacs should be responsive after the animated
GIF has looped once. (Unless there are more frames in the image than
the length of the Emacs image cache.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-05-03 19:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 3:29 bug#23431: 25.0.93; EWW hangs Juliusz Chroboczek
2016-05-03 14:25 ` Kaushal Modi
2016-05-03 14:26 ` Lars Ingebrigtsen
2016-05-03 15:57 ` Lars Ingebrigtsen
2016-05-03 16:20 ` Eli Zaretskii
2016-05-03 16:26 ` Lars Ingebrigtsen
2016-05-03 16:40 ` Eli Zaretskii
2016-05-03 17:04 ` Lars Ingebrigtsen
2016-05-03 17:13 ` Eli Zaretskii
2016-05-03 17:23 ` Lars Ingebrigtsen
2016-05-03 17:34 ` Eli Zaretskii
2016-05-03 17:37 ` Lars Ingebrigtsen
2016-05-03 17:39 ` Lars Ingebrigtsen
2016-05-03 17:41 ` Eli Zaretskii
2016-05-03 17:48 ` Lars Ingebrigtsen
2016-05-03 18:17 ` Lars Ingebrigtsen
2016-05-03 17:17 ` Eli Zaretskii
2016-05-03 17:24 ` Lars Ingebrigtsen
2016-05-03 17:40 ` Eli Zaretskii
2016-05-03 17:43 ` Eli Zaretskii
2016-05-03 17:47 ` Lars Ingebrigtsen
2016-05-03 18:17 ` Lars Ingebrigtsen
2016-05-03 18:33 ` Eli Zaretskii
2016-05-03 16:26 ` Juliusz Chroboczek
2016-05-03 16:27 ` Lars Ingebrigtsen
2016-05-03 16:57 ` Eli Zaretskii
2016-05-03 18:51 ` Glenn Morris
2016-05-03 19:05 ` Lars Ingebrigtsen
2016-05-03 19:16 ` Glenn Morris
2016-05-03 19:23 ` Lars Ingebrigtsen
2016-05-03 20:10 ` Juliusz Chroboczek
2016-05-03 19:31 ` Eli Zaretskii
2016-05-03 19:37 ` Lars Ingebrigtsen [this message]
2016-05-04 2:34 ` Eli Zaretskii
2016-05-04 15:07 ` Lars Ingebrigtsen
2016-05-04 15:24 ` Eli Zaretskii
2016-05-03 20:25 ` Lars Ingebrigtsen
2016-05-03 20:47 ` Lars Ingebrigtsen
2016-05-03 20:53 ` Lars Ingebrigtsen
2016-05-03 21:34 ` Andreas Schwab
2016-05-03 23:37 ` Lars Ingebrigtsen
2016-05-04 2:45 ` Eli Zaretskii
2016-05-04 2:57 ` Juliusz Chroboczek
2016-05-04 14:56 ` Eli Zaretskii
2016-05-04 15:13 ` Nicolas Richard
2016-05-04 15:28 ` Eli Zaretskii
2016-05-04 15:26 ` Juliusz Chroboczek
2016-05-04 15:55 ` Eli Zaretskii
2016-05-04 15:10 ` Lars Ingebrigtsen
2016-05-04 15:16 ` Lars Ingebrigtsen
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=87vb2v0w6x.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=23431@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jch@pps.univ-paris-diderot.fr \
/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).