edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] js interrupt
Date: Fri, 11 Aug 2017 07:52:42 -0400	[thread overview]
Message-ID: <20170711075242.eklhad@comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

Well it helps to talk to one of the duktape developers, doesn't it?
I asked about interrupting runaway js, and there is indeed a mechanism.
DUK_USE_EXEC_TIMEOUT_CHECK
https://github.com/svaarala/duktape/blob/master/config/config-options/DUK_USE_EXEC_TIMEOUT_CHECK.yaml
I'll play with this a bit, and perhaps replace our native method detect and stop code with this, since it is more general.
Of course we still have to retain the interrupt code for fetching files from the internet, which is often the slowest part of a long browse.
I've seen one web page pull down 20 js files.
Anyways, if we have any further questions, enhancements, bug reports etc, I have a duktape contact.

Karl Dahlke

                 reply	other threads:[~2017-08-11 11:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170711075242.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).