From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2602:4b:a4d8:4b00:12bf:48ff:fe7c:5584]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 02B7278414 for ; Thu, 6 Feb 2014 16:28:24 -0800 (PST) From: Chris Brannon To: edbrowse-dev@lists.the-brannons.com Date: Thu, 06 Feb 2014 16:27:51 -0800 Message-ID: <878utnhim0.fsf@mushroom.PK5001Z> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: [Edbrowse-dev] suggest increasing the size argument to JS_NewRuntime X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 00:28:25 -0000 >>From what I can tell, the remaining segfaults all seem to be caused by out-of-memory errors in JS. As an aside, with debug level 2 or greater, edbrowse will print "out of memory" before it crashes. I've increased the size argument to JS_NewRuntime locally, and it helps. I'd suggest bumping it from 4 megabytes to at least 16 or 32. Any objections? Also, I pushed the patch that we discussed earlier today. -- Chris