From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 D467479046 for ; Tue, 3 Nov 2015 17:55:42 -0800 (PST) Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by resqmta-ch2-12v.sys.comcast.net with comcast id dDuv1r0012Fh1PH01Dw47b; Wed, 04 Nov 2015 01:56:04 +0000 Received: from eklhad ([IPv6:2601:405:4080:53:21e:4fff:fec2:a0f1]) by resomta-ch2-08v.sys.comcast.net with comcast id dDw31r00S1DsNmD01Dw49z; Wed, 04 Nov 2015 01:56:04 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.4.2+ Date: Tue, 03 Nov 2015 20:56:03 -0500 Message-ID: <20151003205603.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1446602164; bh=BObm9vN9Jzk7mpPvOu3u1B9KjrDSHUeBBWzxRxmlamc=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=IsZdPnpOql8RyIYSFHHMt7pdd/yO+/4W9y1LdFhtoCsGE8kZLe4Kd7K7XK1M/nTZk fiSoyLqHApjr3O+sACElM9Obr8GEIeMlIi3mHcsLxy9WuJQrxPtbgYk4zvOg6EgVRz dd3M83NCdOtwbHUDRX+GFL7sYqiXaWoleHpVY0ZI67ruFXhFeahXeRN5GsmZOwdorn AjJ9CqnCsq8mX35eiecZFk7ImTTCzlCTI2mUbW5Wl4ieOB/wEkfn5aQ+Hq3p1gYslB v3Zh4DfOziBYBmwQm6Q98vok2sZ8KWy2nH6lsNIO/gdsWC3EeVg1/saplvVrY+gxTj 6JeZ9iqHtirWw== Subject: [Edbrowse-dev] sanity timer X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2015 01:55:43 -0000 With the recent infinite loop, I was wondering if it's worth a few lines of code, and it wouldn't be very many, to put a timer around javascript execution when it runs a script or function. Put alarm(5) before and alarm(0) after. Even under load js shouldn't require 5 seconds of raw cpu to do its calculations,unless something is wrong. This is unix only but that's ok, it's just a backstop for something that should never happen. Or you can just get tired of waiting and hit ^c which is the way it works now. Karl Dahlke