From: Eli Zaretskii <eliz@gnu.org>
To: dal-blazej@onenetbeyond.org
Cc: 54657@debbugs.gnu.org
Subject: bug#54657: 29.0.50; 100% CPU usage with eww on https://blogsurf.io/
Date: Fri, 01 Apr 2022 09:05:02 +0300 [thread overview]
Message-ID: <83tubd5ofl.fsf@gnu.org> (raw)
In-Reply-To: <87fsmx9a23.fsf@onenetbeyond.org> (bug-gnu-emacs@gnu.org)
> Date: Thu, 31 Mar 2022 21:49:40 +0200
> From: dal-blazej--- via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> I was surprised to see that particular site with eww leads to 100% CPU
> usage for 2/3 minutes.
>
> See profiler output below :
>
> ---------- CPU
> 83,835,054 84% - url-http-generic-filter
> 83,687,707 84% - url-http-content-length-after-change-function
> 82,024,107 82% - url-http-activate-callback
> 82,022,955 82% - eww-render
> 55,943,666 56% - eww-display-html
> 30,476,531 30% - funcall-with-delayed-message
> 30,476,531 30% + #<compiled 0x6f61fe78c524dc6>
Type 'v' to see the page's source, and you will immediately understand
why. 99% of that page is a huge JS script that is basically a single
humongous line whose length is 12MB. Even Less chokes on this page,
just showing its end on the screen.
IOW, IMO this is just another instance of the well-known problem in
the display engine with very long lines.
Maybe EWW could be smarter when displaying pages with JS scripts, but
how many pages out there have something similar?
next prev parent reply other threads:[~2022-04-01 6:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 19:49 bug#54657: 29.0.50; 100% CPU usage with eww on https://blogsurf.io/ dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 6:05 ` Eli Zaretskii [this message]
2022-04-02 15:35 ` Lars Ingebrigtsen
2022-04-02 15:45 ` Eli Zaretskii
2022-04-02 16:04 ` Lars Ingebrigtsen
2022-04-02 16:18 ` Eli Zaretskii
2022-04-02 16:29 ` Lars Ingebrigtsen
2022-04-02 17:17 ` Eli Zaretskii
2022-04-03 11:52 ` Lars Ingebrigtsen
2022-04-03 12:06 ` Andreas Schwab
2022-04-03 12:22 ` Lars Ingebrigtsen
2022-04-03 13:57 ` Andreas Schwab
2022-04-03 14:55 ` Lars Ingebrigtsen
2022-04-03 15:05 ` Eli Zaretskii
2022-04-04 10:31 ` Lars Ingebrigtsen
2022-04-21 14:23 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-03 15:05 ` Andreas Schwab
2022-04-03 12:07 ` Eli Zaretskii
2022-04-03 12:21 ` Eli Zaretskii
2022-04-03 12:25 ` Lars Ingebrigtsen
2022-04-03 12:21 ` Lars Ingebrigtsen
2022-04-03 12:44 ` Eli Zaretskii
2022-04-02 15:33 ` Lars Ingebrigtsen
2022-04-02 23:55 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87lewnt4td.fsf@onenetbeyond.org>
2022-04-03 11:51 ` 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=83tubd5ofl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54657@debbugs.gnu.org \
--cc=dal-blazej@onenetbeyond.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 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.