URGENT!!! CRASH 5.2a RC1 (Win7): Opening Tools > Collections

Rosie Perera
Rosie Perera Member Posts: 26,202 ✭✭✭✭✭

I had returned to my computer after some time away. Logos was already running. I switched back to Logos and merely did Tools > Collections, and Logos crashed. The error was:

Error ID: 4422
Error detail: MethodBehaviorConverterException: Exception executing LDLS4.ToolModel.Open

Libronix.Utility.Windows.Converters.MethodBehaviorConverter+MethodBehaviorConverterException: Exception executing LDLS4.ToolModel.Open ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.

Log files attached.

EDIT: It's repeatable on my machine. Every time I try to open the Collections tool, Logos crashes. Even if I start Logos up with a blank layout. Here is the log file for when I do the latter:

5672.LogosCrash L5.2a RC1 20140323b.zip

I'm dead in the water, cannot use collections. This is a show stopper bug! Please do not release RC1. Fix this crash. Thank you!

Comments

  • Jack Caviness
    Jack Caviness MVP Posts: 13,491

    No crash 5.2a RC-1 Mac

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    Can you access your collections through the Library without the crash? Just wondering if it's a data issue or something else.

  • Rosie Perera
    Rosie Perera Member Posts: 26,202 ✭✭✭✭✭

    No crash 5.2a RC-1 Mac

    I'm sure there's no crash in general on Windows either. Perhaps it has something to do with what or how many collections I have.

    Can you access your collections through the Library without the crash? Just wondering if it's a data issue or something else.

    Good thought. I can access the Collections dropdown in the Library, and can select one and the Library displays its contents correctly. So I just can't edit any collections. But it looks like my Collections database is not corrupt.

    I'm willing to send along whatever other supporting files are needed to debug this. Logos, would my ResourceCollectionManager.db be sufficient? Here it is: 4174.ResourceCollectionManager.db

  • Randy W. Sims
    Randy W. Sims Member Posts: 2,272 ✭✭✭

    2014-03-23 18:30:46.8433 1 Info PanelViewModel Got panel settings for History: Columns=Image:30;Type:100;Title:402;Authors:134;UserTags:511;UserRating:100;AbbreviatedTitle:200;Publishers:100;Series:100;Subjects:512.72727272727263|SelectedCollection=CollectionId%3d6e199112-56b7-45ba-a993-ba89e180bf81%7cTitle%3dTopical%2520Bible%2520Indexes|SortMode=Title|View=Details

    I tried duplicating your settings, but can't find a way replicate the crash. May be something specific to that collection, Topical Bible Indexes? Hopefully the smart people will show up soon.

  • I'm dead in the water, cannot use collections.

    Apologies: unable to replicate crash using Logos 5.2a RC1 on Windows 7 with Details View in Library: opened to Blank Layout, then clicked Tools Collections

    What grid view is being used in Library ? Cover, Tile, Details ?

    Keep Smiling [:)]

  • Rosie Perera
    Rosie Perera Member Posts: 26,202 ✭✭✭✭✭

    What grid view is being used in Library ? Cover, Tile, Details ?

    Details. But it doesn't matter. Library is able to show Collections just fine no matter which I choose. And Tools > Collections crashes whatever view the Library was in.

    My Collections tab was left in Details view last time I was able to bring it up, since that's the view I always use.

    I suspect it's a coding bug. The error gives a clue:

    Libronix.Utility.Windows.Converters.MethodBehaviorConverter+MethodBehaviorConverterException: Exception executing LDLS4.ToolModel.Open ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.

    Similar to passing a null pointer to a function that expects a legitimate address value. Probably some uninitialized variable. Weird that it's not reproducible by others, though. I have several hundred collections. I wonder if there's a certain bit of code that only gets executed under certain circumstances?

  • I have several hundred collections. I wonder if there's a certain bit of code that only gets executed under certain circumstances?

    Attached Resource Collections database has 190 collections.  Noticed four "Unnamed Collection" that includes last three collections with null rule for filtering library.

    Wonder about using https://documents.logos.com/ to delete all "Unnamed Collection" documents then launch Logos 5 to sync changes, followed by trying Tools Collections ?

    Keep Smiling [:)]

  • Rosie Perera
    Rosie Perera Member Posts: 26,202 ✭✭✭✭✭

    Attached Resource Collections database has 190 collections.  Noticed four "Unnamed Collection" that includes last three collections with null rule for filtering library.

    Wonder about using https://documents.logos.com/ to delete all "Unnamed Collection" documents then launch Logos 5 to sync changes, followed by trying Tools Collections ?

    Very good theory! I tried doing that, but Logos still crashes when I try to open Collections tool. Here is collection manager db now, presumably without those Unnamed Collections, though I no longer have the db software on my machine to open it and check and can't even remember what it's called.

    [DELETED file previously attached]

    EDIT: I went again to https://documents.logos.com/  and realized some of the "Unnamed Collection" documents had reappeared, and in fact there was yet another one that I discovered after deleting those again and restarting Logos and forcing a sync. So all of them are now really and truly gone, but Logos still crashes when I try to open the Collections tool. Could you check and see if any of my other collections have null rules?

    Here now is my collections manager db file one more time.

    1346.ResourceCollectionManager.db

  • Here is collection manager db now, presumably without those Unnamed Collections, though I no longer have the db software on my machine to open it and check and can't even remember what it's called.

    Noticed row id change for all "Unnamed Collection"

    First attached database file:

    Second attached database file:

    Edit: Third attached database file has 188 collections with two "Unnamed Collection"

    Keep Smiling [:)]

  • Rosie Perera
    Rosie Perera Member Posts: 26,202 ✭✭✭✭✭

    Edit: Third attached database file has 188 collections with two "Unnamed Collection"

    Hmm, interesting. documents.logos.com only shows one "Unnamed Collection" so there's one in there which is inaccessible from there. Wondering what SyncState = 1 and a blank SyncRevision field mean?

    I also recall that Logos creates a default "Unnamed Collection" for you which you can't delete. It's the one that you're editing when you go to the Collections tab the first time you open it up.

    And thanks for reminding me it was SQLite that I used to have on my old computer. Wondering if it's possible to delete rows using SQLite without wreaking havoc? I'm afraid to try.

    EDIT: Downloaded SQLite Manager extension for Firefox. Can't figure out how to run it, to be able to open a db with it. How do you do that?

    EDIT2: Never mind. Figured it out. First had to turn on menu bar, then Tools > SQLite Manager.

    So I did an experiment and deleted that "Unnamed Collection" with SyncState = 1. I'm not sure that doesn't mess things up, just doing that. But Logos still crashes. (Don't worry. I'd saved a copy of the .db file and restored it afterwards.)

  • So I did an experiment and deleted that "Unnamed Collection" with SyncState = 1. I'm not sure that doesn't mess things up, just doing that. But Logos still crashes. (Don't worry. I'd saved a copy of the .db file and restored it afterwards.)

    One experiment idea is:

    1. Close Logos (so does not sync)
    2. Use https://documents.logos.com/ to delete all "Unnamed Collection" 
    3. Rename .db file and associated journal
    4. Open Logos 5.2a RC 1 to a blank layout, which will recreate .db with journal plus download collections from Logos servers
    5. When sync is finished, use Library to verify 186 collections are in drop down list
    6. Try opening Tools Collection

    FYI: personally do not have "Unnamed Collection" in 339 collections.

    Keep Smiling [:)]

  • Rosie Perera
    Rosie Perera Member Posts: 26,202 ✭✭✭✭✭

    One experiment idea is:

    1. Close Logos (so does not sync)
    2. Use https://documents.logos.com/ to delete all "Unnamed Collection" 
    3. Rename .db file and associated journal
    4. Open Logos 5.2a RC 1 to a blank layout, which will recreate .db with journal plus download collections from Logos servers
    5. When sync is finished, use Library to verify 186 collections are in drop down list
    6. Try opening Tools Collection

    Another great suggestion. Tried it, and "Unnamed Collection" was gone for Library collections dropdown list. But Tools Collections still crashed.

  • fgh
    fgh Member Posts: 8,948 ✭✭✭

    Can you open Collections from the Command box? 

    I'm asking because that's worked for me the last few months when every click on Guides caused a crash.

    Mac Pro (late 2013) OS 12.6.2

  • Thomas Ball
    Thomas Ball Member, Logos Employee Posts: 3,261
  • Thomas Ball
    Thomas Ball Member, Logos Employee Posts: 3,261

    Dev has figured out the crash. This should be fixed in an update. I've provided Rosie with instructions fixing the problem in her case specifically. 

     

  • Dylan Rondeau
    Dylan Rondeau Member, Logos Employee Posts: 1,401

    Dev has figured out the crash. This should be fixed in an update.

    Update is now available, this is fixed in 5.2a RC 2.

    Dylan Rondeau, Software Tester

    Enable Logging: Mac | Windows (Right-click "Save As...")

  • Rosie Perera
    Rosie Perera Member Posts: 26,202 ✭✭✭✭✭

    Thanks Tommy and Dev team for your excellent troubleshooting assistance and providing me a temporary fix until RC2 came out (which turned out to be nearly immediately anyway).