From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44])
	by hurricane.the-brannons.com (Postfix) with ESMTPS id CC81777E34
	for <edbrowse-dev@edbrowse.org>; Wed, 11 Sep 2019 07:03:33 -0700 (PDT)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111])
	by resqmta-ch2-12v.sys.comcast.net with ESMTP
	id 81edinCbWyVMu83DYiPJwD; Wed, 11 Sep 2019 14:03:32 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
	s=20190202a; t=1568210612;
	bh=jme2a6PSTUhZJbo/6B0rgzKdNyolAIw4CKWGJ75vDD8=;
	h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID:
	 Mime-Version:Content-Type;
	b=ela+R4+mTy6CdzR3GT/orFUcvyC+Runle/+DLaxPuAOIf65dca8sAMJEjwbP9LgAg
	 H8nwgsQ8NG3BI5R0oFJVJls7bC8UonEd1z1ik+b5f8dwbhY0D/TIT/7EJY+tUkZEKR
	 zTSsEEXyCizVq8SRhjaGRA1CL0o1dWT848bnUObaGNUXMdOD+Q6tXGp4KG/1nC6qgv
	 NclE1vv3YRYkGyEeACp+y29xB94+Th06LCsLa6buIucRI5Z2azaDXot+XE6yNUjSQt
	 dLHLu0yL7DAoJ+UaDWqrf05zpsJvfufVtZ7xTejAvEU8hSdd82aBUk9UQ+oVW1O+e+
	 ngmZJo9OTukmw==
Received: from unknown ([IPv6:2601:408:c303:3f49:21e:4fff:fec2:a0f1])
	by resomta-ch2-15v.sys.comcast.net with ESMTPSA
	id 83DXiko4Z3u9J83DYi7klp; Wed, 11 Sep 2019 14:03:32 +0000
X-Xfinity-VMeta: sc=0;st=legit
To:edbrowse-dev@edbrowse.org
From: Karl Dahlke <eklhad@comcast.net>
Reply-to: Karl Dahlke <eklhad@comcast.net>
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)
Subject: [edbrowse-dev] Hard Interrupt
Date: Wed, 11 Sep 2019 10:03:31 -0400
Message-ID: <20190811100331.eklhad@comcast.net>
X-BeenThere: edbrowse-dev@edbrowse.org
List-Id: Edbrowse Development List <edbrowse-dev.edbrowse.org>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

It's always fun to play with threads.

A week ago I mentioned a site that falls into an infinite js loop,
and sadly this is not unusual.
Nothing to do but kill edbrowse and start over.

Well I'm trying something new that is not great but better than sigquit or sigterm.
If you keep hitting ^C, and you've been locked out for 45 seconds,
I kill the current thread and spawn a new one.
You are back to edbrowse, and you can review all your files in all your sessions,
and call up new web pages etc.
However, javascript is disabled.
duktape was forcibly stopped in the middle of operations, and it has no way to recover from that.
You can turn it on again, but it's at your own risk.
Could lead to a seg fault.

I would probably turn javascript on again long enough to run snapshot(), to start debugging.

After this hard interrupt, ^c doesn't work any more, at all.
I don't know why.
Something about threads and signals and such I'm sure.
So you can't interrupt out of anything else.
You probably want to clean up everything and restart edbrowse.

to test, make an html file that includes

<script>
while(true) {
document.body.style;
}
</script>

Karl Dahlke