From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by hurricane.the-brannons.com (Postfix) with ESMTP id 9784B78417 for ; Fri, 7 Feb 2014 06:01:49 -0800 (PST) Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta15.westchester.pa.mail.comcast.net with comcast id PRo31n0041uE5Es5FS1ESe; Fri, 07 Feb 2014 14:01:14 +0000 Received: from eklhad ([107.5.36.150]) by omta16.westchester.pa.mail.comcast.net with comcast id PS1E1n00c3EMmQj3cS1Eom; Fri, 07 Feb 2014 14:01:14 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Fri, 07 Feb 2014 09:01:14 -0500 Message-ID: <20140107090114.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=q20121106; t=1391781674; bh=AoYDfyUOsqSBu7QsoLHoIB4ftRlUJ8unFoMQnBJbZuY=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=U7xTbTKbosQ6BCp64QDLcEoR+8l5w/7UZg0CyIuasMKI5kzIAU02BT7pxmVq63YFY FapI6ZfrybZ+bSHic03nEluvNLDoGYTz3ECAMs0ZtUXffRYUq/TuaVxE1wUb515ZpJ KkWWYKV/ltxD9f4gnhVZjRwWQPwFrfQdkzcgK2gNPjcxWQWOIArpAwN03zH0RKIoSF w73qAha11Sj0jYgDc2czXSQHZCloViy0cDyj3YL69cIGyJgJ7fUYXqtJ4RFWfLTIp9 bcOFxl+VECUu637GcdDXMb7vfKxQ72TOj/95iefsUs3pVc41Rl2amDSHSxJ/hK0tFd lOB2JrN4N2qSQ== Subject: [Edbrowse-dev] Error Legs X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Karl Dahlke List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 14:01:49 -0000 Ok, I follow what you're saying. The expedient approach is to wrapper some of the js calls, the way I wrapper malloc, to simply exit upon null, and I think that would be fine for now, provided the runtime pool is pushed up to 64 meg. It just wouldn't come up very often. People download huge files, but that doesn't consume huge javascript space. Web pages come in a certain size, and usually don't include memory intensive js. Later versions can, perhaps, be more graceful about these allocation errors, but I think size_t issues, better dom support, ajax, plugins (particularly flash), and imap, are all higher priority. For now, a version that never ever segfaults would be lovely. Karl Dahlke