From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 769E121DE01 for ; Fri, 4 Dec 2015 14:09:52 -0800 (PST) Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-05v.sys.comcast.net with comcast id paAq1r0012D5gil01aBQau; Fri, 04 Dec 2015 22:11:24 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-06v.sys.comcast.net with comcast id paBQ1r0012MDcd701aBQt0; Fri, 04 Dec 2015 22:11:24 +0000 To: edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <87vb8gra8x.fsf@mushroom.localdomain> User-Agent: edbrowse/3.5.4.2+ Date: Fri, 04 Dec 2015 17:11:23 -0500 Message-ID: <20151104171123.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=1449267084; bh=jWXqg6Qldt+TRAoZs/UFz/rQLMgg7ankcCWFnpt0Bps=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=TyeT72Vov3ndy+jyPTSarNZQByixgMu5ki49+jFGw2Mm8D1a869ugnGfQUEfELl+1 NGCbPDep/bQz56fJDwQ6yRT431mc48qN+TVeL/16RyFcgwXUNVfpHJCpOLWL5h0jma g95wULbeFi4TGDCLNQYWeZH5BQa94fnWolyuabOoW5AeDTS8Ol4PNg1yHRlAKf4oJY 7H4li7OvBreTPWJCfw4nkr0LcYnv2qYa6kBCEHAUheqd7MGL6Hd+jQtmXTklWJ8BNP EuDdHnqWsjB5sLPgBDDJ2XmGSpKahZK2GaZjIPoJlUPQgt7IvsS8kVGjNYPijsggSp teDHRikI5dU1w== Subject: [Edbrowse-dev] jquery v2 and an interesting seg fault 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: Fri, 04 Dec 2015 22:09:52 -0000 > document.nodeType = 9; > document.implementation = {}; > document.location = {}; The first two are fine and (theoretically) harmless. The third is not a good idea, as document.location is set at run time and is a URL object equal to the url of the page you are browsing. My latest push adds the first two lines. The seg fault I cannot reproduce, even with these lines added, at least not on the fanfiction home page. Perhaps you traveled down the path a ways and read a book or some such. Still I get a glimpse of the problem from your backtrace. Somehow and for some reason js is trying to remove a node from beneath another node that has no children. Obviously this should never happen, but it does, or does for you, so my push allows for that. Karl Dahlke