ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: context/mtxrun makes Firefox eat up cpu
Date: Thu, 29 Oct 2020 11:48:15 -0400 (EDT)	[thread overview]
Message-ID: <nycvar.YAK.7.78.908.2010291141300.95342@nqv-guvaxcnq> (raw)
In-Reply-To: <CACNy3NAD9nngav9wnFSiFG1FmAkEv-eXQ4Sk81n06mp56ayqYg@mail.gmail.com>

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
___________________________________________________________________________________

  parent reply	other threads:[~2020-10-29 15:48 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
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 [this message]
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=nycvar.YAK.7.78.908.2010291141300.95342@nqv-guvaxcnq \
    --to=adityam@umich.edu \
    --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).