GNU bug report logs -
#54657
29.0.50; 100% CPU usage with eww on https://blogsurf.io/
Previous Next
Reported by: dal-blazej <at> onenetbeyond.org
Date: Thu, 31 Mar 2022 19:50:01 UTC
Severity: normal
Tags: moreinfo
Found in version 29.0.50
Done: dal-blazej <at> onenetbeyond.org
Bug is archived. No further changes may be made.
Full log
Message #52 received at 54657 <at> debbugs.gnu.org (full text, mbox):
> Resent-From: Eli Zaretskii <eliz <at> gnu.org>
> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
> Resent-CC: bug-gnu-emacs <at> gnu.org
> Resent-Sender: help-debbugs <at> gnu.org
> Date: Sun, 03 Apr 2022 15:07:53 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 54657 <at> debbugs.gnu.org, dal-blazej <at> onenetbeyond.org
>
> > From: Lars Ingebrigtsen <larsi <at> gnus.org>
> > Cc: dal-blazej <at> onenetbeyond.org, 54657 <at> debbugs.gnu.org
> > Date: Sun, 03 Apr 2022 13:52:42 +0200
> >
> > 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.
And in addition, I hope you verified that when
libxml-parse-html-region finishes in your case after so little time,
it returns the document's DOM, not something trivial?
This bug report was last modified 3 years and 30 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.