> 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.

If I understand you correctly, here's what I've tried:
1. open firefox, open no webpages, so there's only one about:blank
2. ctrl+alt+2, login, `context --help`
3. (in the text interface) `htop`, firefox cpu usage rises to 100% after ~1s.


On Fri, 30 Oct 2020 at 10:07, Taco Hoekwater <taco@elvenkind.com> wrote:


> 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
___________________________________________________________________________________