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

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?

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

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.)

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.

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).