From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by hurricane.the-brannons.com (Postfix) with ESMTP id 1835278430 for ; Fri, 7 Feb 2014 12:07:15 -0800 (PST) Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta09.westchester.pa.mail.comcast.net with comcast id PXVl1n0040QuhwU59Y6gdv; Fri, 07 Feb 2014 20:06:40 +0000 Received: from eklhad ([107.5.36.150]) by omta02.westchester.pa.mail.comcast.net with comcast id PY6f1n00R3EMmQj3NY6gQW; Fri, 07 Feb 2014 20:06:40 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Fri, 07 Feb 2014 15:06:40 -0500 Message-ID: <20140107150640.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=1391803600; bh=OP5/bF0xQ7zdCo4upIhKzR4DR6Ij/TdGdv89/OAuPss=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=IBhDxdNupDsPohMNq7on2kEiU2ajTvmRZQ3zMEDReTVryleZVel7zKuxLMqHuQDzJ VJN0f9hdwbgtJ/mJ34LD1ZG6Z4r6gFyrhSyi8N56W/+Kqt7vJA2chcz3QOYo/N3aei 49Z0YmlgBA/MhjXeJUFymZpAvWghjINNy1xPGbvG2R4bDlTAmiXm7wC8pO9kErrwrW L4h2tHMM7FwVeCJT/F34JbgO7lwnuIazJOmO7ZxFFaXNeDdEhGDJJeHH/RbjMERXNg cLgn5uMHcxfQc4Wi4nhjtZnm8miY068XpuPfwfhe04gY8QGRopDhzqrCV1afIWYH9m RpKUFvog1ICxQ== 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 20:07:15 -0000 > You're still running a 32-bit machine / OS, right? I run 64-bit, so > maybe the difference is pointer size. Well if that relatively small difference could push you over the edge, then likely I would get the memory error if I change my runtime pool from 4 meg to 2 meg; and I do. Therefore, real world websites can consume 4 meg js; and I do remember youtube use to cause a lot of the segfaults. I suggest we push the size up to 16 meg, or perhaps 32. Karl Dahlke