From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47895@debbugs.gnu.org
Subject: bug#47895: 28.0.50; Emacs should only animate images that are visible
Date: Mon, 19 Apr 2021 22:49:55 +0200 [thread overview]
Message-ID: <87mttum230.fsf@gnus.org> (raw)
In-Reply-To: <8335vmrux2.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 19 Apr 2021 21:28:09 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I'd be interested to see a backtrace for such animation of an image
> that is not on display. In general, since animation is triggered (I
> think) when the image is being prepared for redisplay, what you
> describe shouldn't be happening. If it dies indeed happen, I have a
> couple of guesses how that could be triggered, but it would be nice to
> see evidence.
I unfortunately don't have the time to debug right now, but it's easy
enough to reproduce:
(progn
(eww "https://lars.ingebrigtsen.no/wp-content/uploads/2018/03/candid.gif")
(bury-buffer))
This will leave you with an Emacs that uses at least 99% CPU, even if
the eww buffer isn't even displayed. (At least on this Debian/bullseye
system, starting from -Q.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-04-19 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 18:19 bug#47895: 28.0.50; Emacs should only animate images that are visible Lars Ingebrigtsen
2021-04-19 18:28 ` Eli Zaretskii
2021-04-19 20:49 ` Lars Ingebrigtsen [this message]
2021-04-20 2:24 ` Eli Zaretskii
2021-04-20 13:51 ` Eli Zaretskii
2021-04-25 18:48 ` Lars Ingebrigtsen
2021-04-25 19:01 ` Eli Zaretskii
2021-04-25 19:07 ` Lars Ingebrigtsen
[not found] ` <YIciJ+1fSjJGcu+P@faroe.holly.idiocy.org>
2021-04-27 15:51 ` Alan Third
2021-04-27 23:23 ` Lars Ingebrigtsen
2021-05-02 9:35 ` Eli Zaretskii
2021-05-03 9:52 ` 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=87mttum230.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47895@debbugs.gnu.org \
--cc=eliz@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).