Re: [Edbrowse-dev] Finding cycles in the tree

[Kevin Carhart <kevin@carhart.net>]

I hope to be on the beat more over the next few days.  I know you asked 
about the attributes routines too.  I'll be trying to find out what I can 
find out tonight and tomorrow.
Kevin


  On Thu, 26 Jan 2017, Karl Dahlke wrote:

> 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-departments-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
>

--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists