From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 54657@debbugs.gnu.org, dal-blazej@onenetbeyond.org
Subject: bug#54657: 29.0.50; 100% CPU usage with eww on https://blogsurf.io/
Date: Sun, 03 Apr 2022 15:07:53 +0300 [thread overview]
Message-ID: <83pmly2wva.fsf@gnu.org> (raw)
In-Reply-To: <871qyel6yd.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 03 Apr 2022 13:52:42 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: dal-blazej@onenetbeyond.org, 54657@debbugs.gnu.org
> Date: Sun, 03 Apr 2022 13:52:42 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > According to what I see here, libxml-parse-html-region is indeed the
> > part that takes most of the CPU time, and I measured about 30 sec here
> > it took it to parse that page. If you see something very different,
> > maybe the important factor here is the version of libxml2?
>
> Wow. If you call
>
> (benchmark-run 1 (libxml-parse-html-region (point-min) (point-max)))
>
> in the 12MB source buffer for that page, it reports 30 seconds? It
> reports 0.01 seconds for me.
I didn't do the above, I just stepped through eww-display-html in
Edebug, and looked at my watch (30 sec is easy to measure without any
instruments).
So what is your version of libxml2? Maybe that is the important
aspect here.
next prev parent reply other threads:[~2022-04-03 12:07 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
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 [this message]
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=83pmly2wva.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54657@debbugs.gnu.org \
--cc=dal-blazej@onenetbeyond.org \
--cc=larsi@gnus.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.