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: Thu, 29 Oct 2020 12:00:09 +0100 [thread overview]
Message-ID: <B2CB0189-F024-4E3A-A708-286D88FD4972@elvenkind.com> (raw)
In-Reply-To: <CACNy3NAD9nngav9wnFSiFG1FmAkEv-eXQ4Sk81n06mp56ayqYg@mail.gmail.com>
> On 29 Oct 2020, at 11:29, Sylvain Hubert <champignoom@gmail.com> wrote:
>
> Hi,
>
> sorry if this is not the best place to file a bug but I found no working bug tracker for context.
Should you not be looking for a bug tracker for firefox instead?
It looks like firefox in safe mode is perhaps trying to do something with (or waiting for ?) a shell command called ‘context’, which is presumably not related to ‘our’ ConTeXt.
You can test that by (temporarily) redirecting the ‘context’ command from ‘luametatex’ to ‘ls’ (but keep it at the same path), and see if the problem persists. If so, then it is the actual name giving problems, and then can you should file a firefox bug report because then it has nothing to do with ConText itself.
But even if the above is not the actual issue, it still sounds like a firefox problem to me.
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-29 11:00 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 [this message]
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
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=B2CB0189-F024-4E3A-A708-286D88FD4972@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).