Hi aditya,

> It is possible for you to check on a fresh install of manjaro in a virtual machine to rule out the possibility that something else in your system is causing this behavior.
I remember trying context while browsing the wiki before so it should work normally in a brand new environment, but I don't think it's reasonable to install a brand new distro just to make sure that 'context --help' can work normally, no matter how problematic the current distro is, as long as it does not prevent commands from displaying help messages.

On Thu, 29 Oct 2020 at 16:50, Aditya Mahajan <adityam@umich.edu> wrote:
On Thu, 29 Oct 2020, Sylvain Hubert wrote:

> Hi,
>
> sorry if this is not the best place to file a bug but I found no working
> bug tracker for context.
>
> Environment:
> Manjaro 20.1.2, context 2020.09.20 23:02, firefox 82.0
>
> Step to reproduce:
> 1. `firefox --safe-mode  # start firefox without add-ons`
> 2.a`context --version  # or --help, or without arguments`
> 2.b or: `mtxrun --script font --list --all`
>
> Expected behavior:
> Nothing surprising should happen.
>
> Actual behavior:
> Firefox suddenly eats 100% of cpu

I cannot reproduce this behavior (I am on manjaro but using firefox 81 rather than 82). My environment:

$uname -a
Linux hostname 5.4.67-1-MANJARO #1 SMP PREEMPT Wed Sep 23 14:20:18 UTC 2020 x86_64 GNU/Linux

$firefox --version
Mozilla Firefox 81.0

$context --version
mtx-context     | ConTeXt Process Management 1.03
mtx-context     |
mtx-context     | main context file: /opt/luametatex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context     | current version: 2020.09.15 18:11
mtx-context     | main context file: /opt/luametatex/texmf-context/tex/context/base/mkiv/context.mkxl
mtx-context     | current version: 2020.09.15 18:11

I followed your steps:
1. start `firefox --safe-mode`
2. On a different terminal, open htop and filter `firefox` so I can view firefox's CPU usage.
3. Run `mtxrun --script font --list --all`

The CPU usage of firefox does not change in any appreciable way (it was 0% and remains 0%).

It is possible for you to check on a fresh install of manjaro in a virtual machine to rule out the possibility that something else in your system is causing this behavior.

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