From: Sylvain Hubert <champignoom@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: context/mtxrun makes Firefox eat up cpu
Date: Thu, 5 Nov 2020 11:48:29 +0100 [thread overview]
Message-ID: <CACNy3NC=AbWk7z_d+FkjZ0oH4wOEWzcp8=Qo8849Bx76CFAcNw@mail.gmail.com> (raw)
In-Reply-To: <CACNy3NCnrywTj=NT-XZsCGFE+f8HYjLfG1MjA5A5C=ZJtvvJvQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1227 bytes --]
After dozens of compilations of various minimal examples using the newly
installed context, the problem reappeared.
Removing tex/texmf-cache does not help.
Does anyone know what files context modifies apart from tex/texmf-cache?
Sylvain
On Wed, 4 Nov 2020 at 16:01, Sylvain Hubert <champignoom@gmail.com> wrote:
> The problem disappeared after a fresh installation of context with
> everything else untouched.
>
> On Thu, 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.
>>
>> 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've noticed that `context` symlinks to `luametatex`, but the latter
>> itself does not trigger the bug, neither do `luatex` or `latex`, so I
>> believe this is a context-specific thing.
>>
>> Best,
>> Sylvain
>>
>
[-- Attachment #1.2: Type: text/html, Size: 2128 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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-11-05 10: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
2020-10-29 16:56 ` Sylvain Hubert
2020-11-04 15:01 ` Sylvain Hubert
2020-11-05 10:48 ` Sylvain Hubert [this message]
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='CACNy3NC=AbWk7z_d+FkjZ0oH4wOEWzcp8=Qo8849Bx76CFAcNw@mail.gmail.com' \
--to=champignoom@gmail.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).