ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: ntg@scorecrow.com
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: context/mtxrun makes Firefox eat up cpu
Date: Fri, 30 Oct 2020 08:34:13 +0000	[thread overview]
Message-ID: <95C43E90-CC1A-430E-85F8-E08C25DB566B@scorecrow.com> (raw)
In-Reply-To: <CACNy3NC2_yo1GkMm1J5nscnRs4m5b51y2Fmt2Tjpw5TY4czDsw@mail.gmail.com>

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.

These symptoms seem to be very similar to yours. Could you please try their steps to reproduce - namely view a video in Firefox - and do so from a fresh reboot without starting or invoking ConTeXt so we can be sure that it is excluded from the equation?

If you get excessive CPU usage following their steps then it is Firefox at fault. If you don't then it might not be - unfortunately it only narrows it down to a 'might'.

Regards,

> On 29 Oct 2020, at 11:44, Sylvain Hubert <champignoom@gmail.com> wrote:
> 
> I've just tried chromium which behaves a bit better but still experiences a sudden raise of cpu usage from <10% to >70% during ~1s.
> I've also noticed that, even without any browser running, each time after I compile a file with `context`, my terminal get stuck for ~1s.
> So I'm pretty sure this is a context bug, probably caused by unnecessary excessive disk operations or something.
> 
> On Thu, 29 Oct 2020 at 12:33, Taco Hoekwater <taco@elvenkind.com> wrote:
> 
> 
> > On 29 Oct 2020, at 12:19, Sylvain Hubert <champignoom@gmail.com> wrote:
> > 
> > And using safe mode here is just to make sure that the problem is not caused by extensions.
> > The annoyance started long before I bothered opening firefox with an extra argument.
> 
> I am baffled then. I do not see the connection, at all. 

--
Bruce Horrocks
Hampshire, UK

___________________________________________________________________________________
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-30  8:34 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 [this message]
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=95C43E90-CC1A-430E-85F8-E08C25DB566B@scorecrow.com \
    --to=ntg@scorecrow.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).