From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] Abort from within duktape when visiting https://www.digicatapult.org.uk/careers
Date: Sat, 07 Dec 2019 17:14:26 -0500 [thread overview]
Message-ID: <20191107171426.eklhad@comcast.net> (raw)
In-Reply-To: <20191207172853.GB194728@toaster>
I'll look at this in one of my insomnia moments.
Such is usually caused by a bad reference or other js runtime error in an unprotected context.
The last time such happened I had to write a protected layer around a call, see jseng-duk.c line 1644.
But of course that might not be what is happening here.
db5
Sometimes shows us going out to make a low level js call but it doesn't return.
Karl Dahlke
next prev parent reply other threads:[~2019-12-07 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 17:28 Adam Thompson
2019-12-07 22:14 ` Karl Dahlke [this message]
2019-12-08 13:53 ` Adam Thompson
2019-12-08 15:26 ` [edbrowse-dev] Abort from within duktape when visiting Karl Dahlke
2019-12-08 16:57 ` Adam Thompson
2019-12-09 10:41 ` Karl Dahlke
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=20191107171426.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.org \
/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).