From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) by hurricane.the-brannons.com (Postfix) with ESMTPS id D34DD7961D for ; Thu, 26 Jan 2017 18:18:17 -0800 (PST) Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99]) by resqmta-ch2-06v.sys.comcast.net with SMTP id Ww6UchLmmTERUWw7ycVr43; Fri, 27 Jan 2017 02:19:02 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1485483542; bh=MbFM0u2EKWmDGX6rarEv7tVBJs8xe3FTJowqeoPH3Zg=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=LRwd8vb0dOt5wnFmfqZ9THcrTdsEtt0yGLX+45qh6P2Ba1aHmONu1TKzZBpNVBTPo 3+4EcOmuxPA/S+IGz9mom3nESdCrcLX68kVpNw86WGaAfGOWNEnTDa1ClCVAnIqOaa 0lAP5mo1yjgLrRS2wo0SkHL8jP4GVgl4gJj48bcHgTWQqxw8I2Aehx2LJ54zJobKBv mvvJZvbtW9dQjGfgOVifFjyrkJ6QmNB4d1WIPOJ4JlQmR9Ayys4pswTxl3B4seNQvi +eGB9+XMBLjxCQRHGWRMpR9Eona8ObQNEhJkgqM6guwSa+iLLMZVsrZJxiQxqwQWMg 6NHgT5CJUpC8w== Received: from unknown ([IPv6:2601:408:c301:784d:21e:4fff:fec2:a0f1]) by resomta-ch2-03v.sys.comcast.net with SMTP id Ww7xc73BEozfRWw7xcQrHC; Fri, 27 Jan 2017 02:19:02 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.6.2+ Date: Thu, 26 Jan 2017 21:19:01 -0500 Message-ID: <20170026211901.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=nextpart-eb-962724 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfJuqu++WtFeN3PeR24t6BVvjpuXagRy3RWQE8z68at46tgaqOgtLuDC3E25sFFEJUwehfy1XWLY2UUofYZr5WDOQw2IJC6m/tJeYdr4F4sOLpdrMJm3/ L8DITgxDe/g5AFpfObFTq/bx2BoHrO/biKimGDJBeimkkyoWcoBbQJgA Subject: [Edbrowse-dev] Finding cycles in the tree X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 02:18:18 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --nextpart-eb-962724 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable A few words about the last push. Of late we've been seeing more seg faults, very difficult to track = down, seeming to involve infinite recursion. The latest is from this website. https://www.washingtonpost.com/news/josh-rogin/wp/2017/01/26/the-state-d= epartments-entire-senior-management-team-just-resigned Without my last push, it waits for a while, until some stack blows up, = then seg faults. The problem is that a node that is already in the tree is being linked = to another node in the tree. The next traversal goes on forever. So now, when I link A into B, if A has a parent, i.e. A is already in = the tree, I give an explanation at db3, and don't make the link. That fixes the seg fault, and probably the seg fault in other sites. This leaves some questions however - why is the js trying to do that? Is it a mistake cause by our imperfect DOM, or did an earlier routine = fail and if that had completed then this link would make more sense? Or is that what is suppose to happen, and I'm suppose to unlink it from = its current location and then link it to the new location? Is there in implicit remove before the link? I don't know. Anyways, with this push, the aforementioned website, at debug 3, gives = this message. linkage cycle, cannot link div 1414 into body 198 before div 203, as = the child already has parent div 203 Aborting the link, some data may not be rendered. The push also adds more information at db4, so we can debug, and answer = some of the above questions. You get the edbrowse tree of nodes, and each dynamic link as it is made Karl Dahlke --nextpart-eb-962724--