On Wednesday, September 2, 2020 at 3:24:45 PM UTC-5, k-hen wrote: Ok, got it, will need a bit of time, but will get back to you soon. >
Something strange is going on. Here is what I think I know: The unpacked original file is leo_error_test_01 - cleared - Copy.db. It is about 28.1 MB in size. Opening the file with Leo does work, but the two "node 5660" are not *shown as *clones of each other. Yet they have the same gnx and id(v) is the same for each. Imo, this is likely the ultimate cause of the crash. Saving this .db as a .leo file creates a valid .leo file in which the two "node 5660" are indeed true clones. The bug never appears in the .leo file. Saving the .leo file as a .leo.db file creates a much smaller file, about 1.2 MB. However, in all other respects it appears to be identical to the original .db file. The two "node 5660" are not *shown as *clones of each other, and the bug does manifest itself. My *tentative* conclusion is that there may be a bug in fc.retrieveVnodesFromDb. However, there are no special cases in this code, so what the bug could possibly be is a big mystery. Iirc, Vitalije wrote this code. Any insights would be appreciated. Finally, I note that the .leo files are smaller than the corresponding .db files, so one workaround would be to use the .leo files instead. Presumably, however, there are reasons for using the .db files. 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/9afd5fe4-7fd3-4e68-91d7-283f02367601o%40googlegroups.com.
