all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Madhavan Krishnan <krishnanmadhavan000@gmail.com>
Cc: 45224@debbugs.gnu.org
Subject: bug#45224: 28.0.50; eww and GIFS (cpu usage shoots through the roof)
Date: Tue, 15 Dec 2020 06:41:44 +0100	[thread overview]
Message-ID: <874kkn39t3.fsf@gnus.org> (raw)
In-Reply-To: <877dpkfbf9.fsf@gmail.com> (Madhavan Krishnan's message of "Mon,  14 Dec 2020 19:13:46 +0000")

(Please keep the debbugs address in the Cc headers -- otherwise your
mails won't reach the Emacs bug tracker.)

Madhavan Krishnan <krishnanmadhavan000@gmail.com> writes:

>>> In any case, Emacs should be stopping animations that take too much CPU.
>>> Do you get the "Stopping animation; animation possibly too big"
>>> messages?
>>
>> Nope, I was hardly able to scroll to the end of the page, at any rate my
>> cpu fan kicked in and I killed the entire session.
>
> My bad, I miss spoke yes the message does show "Stopping animation;
> animation possibly too big" (when you scroll the buffer message is gone)
> but the cpu usage is still not down (untill the buffer is killed
> manually)

I see Emacs gradually killing more and more of the animations until
Emacs has reached a usable state again, but it takes a while.  Perhaps
it should be more aggressive in stopping the animations...

Anyway, that's a side issue -- this should really be fixed by making the
GIF animations faster.  I'm not sure whether there's been any work done
on that -- it's been mentioned a few times, but possibly nobody has done
the work?

If I remember correctly, the current code will decode the entire GIF
file for each frame, which is pretty pessimal.  The ImageMagick version
of the animation code keeps a special cache to avoid doing all those
decodings, so perhaps that code can be reused...






  parent reply	other threads:[~2020-12-15  5:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-13 12:45 bug#45224: 28.0.50; eww and GIFS (cpu usage shoots through the roof) Madhavan Krishnan
2020-12-14 17:05 ` Lars Ingebrigtsen
     [not found]   ` <87lfe0fbuv.fsf@gmail.com>
     [not found]     ` <877dpkfbf9.fsf@gmail.com>
2020-12-15  5:41       ` Lars Ingebrigtsen [this message]
2020-12-18  9:39         ` Madhavan Krishnan
2020-12-18  9:48           ` Lars Ingebrigtsen
2021-10-31  1:50             ` Stefan Kangas
2021-10-31 15:10               ` Lars Ingebrigtsen
2022-04-11 16:49                 ` Lars Ingebrigtsen
2022-04-11 17:36                   ` Eli Zaretskii
2021-10-31  1:54             ` Stefan Kangas
2022-04-11 12:38   ` Lars Ingebrigtsen
2022-04-11 12:40     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874kkn39t3.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=45224@debbugs.gnu.org \
    --cc=krishnanmadhavan000@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.