On Mon, Mar 16, 2015 at 5:49 AM, vitalije <[email protected]> wrote
> Some of my last added nodes got the same gnx. One of them had child with the same gnx and that caused Leo to hang. > I can't say which revision I used to write the problematic file. It was one of the revisions after 934537 [March 6] which solved bug #138. Obviously a very serious problem. > I strongly suspect it has something to do with recent changes in Leo write. The write code doesn't allocate gnx's. Leo uses a "holding" logic during reads. Thereafter, gnx's are allocated when a vnode is created. The culprit is more likely to be elsewhere: - Bug 130: About rev c6c14ef on March 2. This changes how Leo calculates the smallest "safe" gnx to use for new nodes. https://github.com/leo-editor/leo-editor/issues/130. It's my prime suspect. - Rev 4ac015f, March 10, removes allow_cloned_sibs logic. - Rev 4cf0945 and following, March 10: remove at.writeVersion5. - Bug 149: Rev 6439440, March 11. Changes how Leo reports recovered nodes. This is a release blocker until we know what happened. Please file a formal bug report. Would it be possible for you to send the original, corrupted, .leo file to me? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
