From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 5A8CD78442 for ; Sun, 9 Feb 2014 02:46:10 -0800 (PST) Received: by mail-wi0-f172.google.com with SMTP id e4so2001968wiv.17 for ; Sun, 09 Feb 2014 02:45:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=mORmC2r/GoqOCLb06DJ3d0Ox6QzD3ApIpbl+nCqsRp4=; b=VzSP0m/3LTEjKdTS557F3qpwej6qEn4DwEQ7J+XZQv0ny2TL3bFfJ2eU+o7rrvlfKm tE4ETu1wZCGxjspOHNh0d8FQz8Mxj4R6vUcLNYKFZ+JiBHrLqJKPiNlgGr9nyRQbndmh ti9lThOH2y2+ofAyPPctrtP68jyKCbEQSkP1ZNQKlA19xtNhUVgHJJl2j5+gHx5ZPsqX RyCkELTaoUs++4WsYCQbvRlXbSAqdKoJqXQCcH06BSzTdS6B+k9N3112f3jX3rHxQfPv KHhAH3YEOOPbr1S0nLniXeCm7BGeMExqEZMdNqbGzhik+DZ9q18WIitK5YPhIerx5kUb iF6Q== X-Received: by 10.180.38.41 with SMTP id d9mr6439326wik.9.1391942729471; Sun, 09 Feb 2014 02:45:29 -0800 (PST) Received: from toaster.adamthompson.me.uk (toaster.adamthompson.me.uk. [2001:8b0:1142:9042::2]) by mx.google.com with ESMTPSA id f1sm27974684wik.1.2014.02.09.02.45.27 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 09 Feb 2014 02:45:28 -0800 (PST) Date: Sun, 9 Feb 2014 10:45:25 +0000 From: Adam Thompson To: Chris Brannon Message-ID: <20140209104525.GB11542@toaster.adamthompson.me.uk> References: <20140107125753.eklhad@comcast.net> <87vbwqg4ty.fsf@mushroom.PK5001Z> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87vbwqg4ty.fsf@mushroom.PK5001Z> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Edbrowse-dev@lists.the-brannons.com Subject: Re: [Edbrowse-dev] Error Legs 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: Sun, 09 Feb 2014 10:46:10 -0000 On Fri, Feb 07, 2014 at 10:23:05AM -0800, Chris Brannon wrote: > Karl Dahlke writes: > > My gut tells me the segfaults might come from somewhere else. > So it is failing with out-of-memory in this case. I'm sure youtube is a > very JS-intensive site, but could there be another reason for the memory > exaustion? I don't know. Not sure, we really need to go through everything and ensure that what needs to be rooted is and what doesn't isn't. Incidentally I bumped my jspool limit up to 64 meg and that example works now. Really it'd be much nicer if we could get js to dynamically grow to deal with this (with an *optional* limit). I'd still prefer it if it just killed the offending context as well (js_DestroyContext and js_GC?). This should mean that everything else can continue and we reclaim the lost memory, or in the worst case just the js side is broken. Either way, it allows the user to save critical work, bookmark pages etc. At the moment, although I agree that not segfaulting is much nicer, the overall outcome is the same; edbrowse goes away taking your unsaved work and other browsing sessions with it. I can try and implement this if people agree. Cheers, Adam.