From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: context/mtxrun makes Firefox eat up cpu
Date: Fri, 30 Oct 2020 10:06:11 +0100 [thread overview]
Message-ID: <6D6F2B63-5B6B-4083-822F-097266E5F6C3@elvenkind.com> (raw)
In-Reply-To: <95C43E90-CC1A-430E-85F8-E08C25DB566B@scorecrow.com>
> On 30 Oct 2020, at 09:34, ntg@scorecrow.com wrote:
>
> Hi Sylvain,
>
> This bug tracker report <https://bugzilla.mozilla.org/show_bug.cgi?id=1599329> describes lagging / freezing (which are symptoms of excessive CPU usage, of course) for versions of Firefox from 70 to 74 inclusive on Manjaro. They also report Chromium seeing the same problem.
This basically says it is a bug in the video driver.
You could test that theory by switching to a text terminal for running the ‘context’ command (assuming the text-only terminal is still accessible in Manjaro) and see whether the output of ‘context —help’ causes lag there as well. Even a really, really crappy video driver should be able to handle the output stream in full-screen text mode, so if it still lags in that environment, that moves the needle toward a problem in ConTeXt (however unlikely Hans and I think that is).
Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-10-30 9:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 10:29 Sylvain Hubert
2020-10-29 11:00 ` Taco Hoekwater
2020-10-29 11:15 ` Sylvain Hubert
2020-10-29 11:19 ` Sylvain Hubert
2020-10-29 11:31 ` Taco Hoekwater
2020-10-29 11:44 ` Sylvain Hubert
2020-10-29 12:55 ` Taco Hoekwater
2020-10-29 14:14 ` Sylvain Hubert
2020-10-29 15:38 ` Taco Hoekwater
2020-10-29 16:44 ` Sylvain Hubert
2020-10-29 17:15 ` Hans Hagen
2020-10-29 14:18 ` Sylvain Hubert
2020-10-29 15:04 ` Hans Hagen
2020-10-30 8:34 ` ntg
2020-10-30 9:06 ` Taco Hoekwater [this message]
2020-10-30 18:44 ` Sylvain Hubert
2020-10-30 19:14 ` Sylvain Hubert
2020-10-30 19:26 ` Hans Hagen
2020-10-30 18:48 ` Sylvain Hubert
2020-10-30 19:28 ` Hans Hagen
2020-10-29 11:26 ` Sylvain Hubert
2020-10-29 15:48 ` Aditya Mahajan
2020-10-29 16:56 ` Sylvain Hubert
2020-11-04 15:01 ` Sylvain Hubert
2020-11-05 10:48 ` Sylvain Hubert
2020-11-05 11:01 ` Taco Hoekwater
2020-11-05 11:49 ` Sylvain Hubert
2020-11-05 11:25 ` Hans Hagen
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=6D6F2B63-5B6B-4083-822F-097266E5F6C3@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).