Not really doing anything specific, I did notice a slowdown and then some syncing before it just shut down. Running L5 SR2 on a 2012 MBP mountain lion. Logs attached.
7624.LogosLogs.gz
John - I noticed that there was a fatal error and that Logos was unable to open a database file… but I don't know which one. Did you just update Logos, or did you have it up and running before the crash?
I updated yesterday to SR 2. Logos had been running 3 hours before the crash with no problems at all. I would speculate that the sync process may have something to do with this problem because scrolling slowed down and I noticed it was syncing. Shortly after it crashed. But of course that is just speculation.
I would speculate that the sync process may have something to do with this problem because scrolling slowed down and I noticed it was syncing. Shortly after it crashed.
FWIW, somewhere buried in the forum is a set of logs that I submitted when Logos crashed under the exact same symptoms. I thought it was having trouble syncing and scrolling slowed down, then it crashed. Hope that helps.
What you say about syncing confirms what I saw in your logs, it crashed syncing. I'm trying to trace back to see which resource it was on.
I have tried to tell L5 to not implement community notes, faithlife notes etc, but I suspect it is a community project...
I have nothing against these projects, I just have chosen not to include them in my studies.
I updated yesterday to SR 2. Logos had been running 3 hours before the crash with no problems at all. I would speculate that the sync process may have something to do with this problem because scrolling slowed down and I noticed it was syncing. Shortly after it crashed. But of course that is just speculation. What you say about syncing confirms what I saw in your logs, it crashed syncing. I'm trying to trace back to see which resource it was on.
It was syncing (had synced many times previously in the log) and when it crashed it was up to this sync item:
Logos.Documents.Contracts.MobileResources.MobileResourceSyncItem
Now.... it can't conclusively be stated that it was the point of syncing that caused the crash because the actual crash error the exception error reports this
System.Data.SQLite.SQLiteException: Unable to open the database fileSystem.Data.SQLite.SQLiteConnection.Open () [0x00000] in <filename unknown>:0
which says that the SQLite database manager was unable to open a database file (obviously), the annoying thing is that Logos does not say which file it was trying to open. This to me is a really ineffective part of the error reporting. So if the two things are linked — trying to sync the MobileResources & Logos crashing on database opening — I don't know.
At the time were you opening a specific resource(s), if so do you remember which?
I wish Logos would report which database was being opened. If we knew (definitively) then we could attempt a database repair — which would be handy, especially if the DB in question was one of the multi-gigabyte ones.
It happened quickly, but I may have been changing commentaries. I don't think it is resource related.
I think the problem may be in the Documents folder, but I'd like to have a level two tech take a look at the situation. John, I've emailed you about this thread.
Thanks for the follow up Tommy.
You're quite welcome.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
