My Logos 5 is consistently crashing within two minutes of opening. I had the problem with Logos 4 and therefore upgraded to Logos 5 Reformed Gold. As far as I can tell, it doesn't matter what I do. Within two minutes of opening, the application crashes. 8547.LogosLogs.jonathanparnell.20140723-152106.zip
Hi Jonathan,
I'm sorry for the trouble. I suspect your index is bad. Before you go to sleep tonight, or whenever you're done with Logos 5 or the computer, rebuild your index. Information on that can be found in the Troubleshooting section of this article: https://www.logos.com/indexing
Welcome to the forums Jonathan. Are you by chance the Jonathan Parnell whose job title is Content Strategist?
Hi, William. Yep.
Thanks. I'll try that!
It's a pleasure to digitally meet you. Thanks for your ministry; I enjoy your work.
Thanks, William! Great to meet you, too!
Friends, I have re-indexed everything, but it continues to crash. It stayed open longer this last time, but when I started using the Passage Guide it cut out again. Any more ideas?!
Hey Tommy, I just made a note below. I rebuilt the index and that did not fix it. Any more ideas? Thanks!
Quickest way now is to call Logos tech support in the morning and have them get on your computer.
800-875-6467
Calling Logos might be your quickest option. Would you be willing to upload your logs again? I'd be interested in seeing if it's the same error as before:
Libronix.Utility.Threading.AsyncWorkException: Unhandled exception in asynchronous work. ---> System.Data.SQLite.SQLiteException: database disk image is malformeddatabase disk image is malformed
Does this happen for every Passage Guide query or only Luke 18?
Thanks, William. It just happened again, this time on Psalm 77 — but really before I could even put the text in.
2500.LogosLogs.jonathanparnell.20140724-092609.zip
The logs are indicating the Index is malformed still. Can you check your computer's hard drive for errors? Run the Check Disk command in the Command Prompt?
Post what results you get and we'll go from there.
It looks to me like he's running on a Mac: 07/24/2014 09:25:08 | INFO | 1 | LDLS4.Macintosh.OurApp | Starting application (5.2a SR-7, version 5.2.1.0171) on Mac OS X 10.9.4.
It is indeed the same Exception as before and it appears it's when Logos tries to look up the Cross References for his passage.
Jonathan, I have a theory that if you created a custom passage guide and removed the Cross Reference section, Logos would probably stop crashing. But obviously that is not optimal. I do not know how Logos syncs those databases--they will have to give you instructions to repair the right database.
If I have time a little bit later today and someone else hasn't figure it out, I can try to debug and figure out possible fixes.
I cannot even get to the passage guide now. This is the note from my Mac I just received when it crashed — when it "Quit Unexpectedly".
Process: Logos [53091]Path: /Applications/Logos.app/Contents/MacOS/LogosIdentifier: com.logos.LogosVersion: 5.2.1.171 (61521.0.171)Code Type: X86 (Native)Parent Process: launchd [155]Responsible: Logos [53091]User ID: 502
Date/Time: 2014-07-24 12:39:45.673 -0500OS Version: Mac OS X 10.9.4 (13E28)Report Version: 11Anonymous UUID: 1EC15E39-F678-1E14-7AF7-D48A3E38762F
Sleep/Wake UUID: A49208D8-B1D4-4FC4-9348-39EB3CA484EF
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)Exception Codes: KERN_INVALID_ADDRESS at 0x00000000730ec898 ...
Duh, sorry about that William.
Jonathan,
On the Mac go to your Utilities folder in the Applications folder. Look for "Disk Utility" check and verify Disk Permissions and fix any errors, as well as the Disk itself. Take a screenshot of the results and post them.
On the Mac go to your Utilities folder in the Applications folder.
Wouldn't it be easier to click Launchpad in the Dock and type dis? [^o)]
Wouldn't it be easier to click Launchpad in the Dock and type dis?
Probably, it would also be easier to go to Spotlight and type disk. I don't always use the shortcut methods because they can involve more interpretation, or assumptions on my part. I don't want to have someone come back and say they didn't see what I expected when taking them down the longer more precise route would have gotten them there correctly.
What I find interesting is that the log says that it's crashing while trying to execute the following query ("select DataTypeName, IndexType, TableName from DataTypes;"), but I cannot find this table (DataTypes) in any of the sqlite databases in my Logos directory.
Regardless of where that table is at, it appears that Logos is not catching the potential SQLiteException if there is a problem with this database query.
07/24/2014 09:26:02 | ERROR | 78 | ApplicationUtility | SQLite Error 11: database corruption at line 50992 of [118a3b3569] 07/24/2014 09:26:02 | ERROR | 78 | ApplicationUtility | SQLite Error 11: statement aborts at 9: [select DataTypeName, IndexType, TableName from DataTypes;] 07/24/2014 09:26:02 | WARN | 78 | AsyncWorkItem | Async work threw exception: System.Data.SQLite.SQLiteException: database disk image is malformed
I made it a little further, but I have not been able to get to the root of where the bad database is.
It looks like the Index that is causing the problem is the Milestone Index, and from what I can tell is in an sqlite database that's in a secret/temporary location. I have not been able to find it on my system yet (I may look more tomorrow).
I think Logos ought to be able to answer this more quickly given the logs (hopefully they still can!), but I have a couple of ideas in the mean time.
1) You might be able to make a new Passage Guide without opening your current one (even if it's the existing). Under Guides in the menu, click "Make a new guide template", drag over a few of the Sections that you would like (or click "Passage Guide" and remove the ones you don't want). Name the Passage Guide (starts off Untitled Guide), and I think Logos will default to using a custom defined PG over the default if you have one. If not, you can always build the Passage Search layout by hand by opening your newly crafted Passage Guide first, then Exegetical Guide, Bible(s), and any other panels you want to open.
2) If that doesn't work, my suggestion in the mean time is to see if it would work to install Logos on another PC, modify your Passage Guide and remove the Cross References section for now, then open your original Logos program after the sync to see if you can get somewhere without it crashing! Perhaps DG has a spare computer you can install Logos on?
Bill
It is one of the milestone index files (/Users/jonathanparnell/Library/Application Support/Logos4/Data/0ecycmns.wni/ResourceManager/logos/*.mstidx); unfortunately, the logs don't identify which one.
Deleting that entire "logos" folder should force them all to be recreated at next startup (I think...); this will involve "Preparing your library" for quite some time.
Removing the Cross References section from the Passage Guide should be a temporary workaround, as it appears that it's the section that's opening the resource that is causing the crash.
Hi Guys,
Am just joining this forum and since Monday 28 July I have received the message L5 quit unexpectedly and all attempts to re-open it has failed. This is part of the detail message it's been given, please help:
Process: Logos [526]Path: /Applications/Logos.app/Contents/MacOS/LogosIdentifier: com.logos.LogosVersion: 5.2.1.171 (61521.0.171)Code Type: X86 (Native)Parent Process: launchd [106]
Date/Time: 2014-08-01 11:30:43.051 +0100OS Version: Mac OS X 10.6.8 (10K549)Report Version: 6
Interval Since Last Report: 23838 secCrashes Since Last Report: 15Per-App Interval Since Last Report: 1022 secPer-App Crashes Since Last Report: 15Anonymous UUID: 45ED69ED-79AE-48BB-A618-4A38E58D0193
Exception Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Application Specific Information:Assertion failed: (libcompiler_rt abort), function __eprintf, file /SourceCache/clang/clang-500.2.79/src/projects/compiler-rt/lib/eprintf.c, line 31.
Hi Sam - and welcome to the forums.
Sorry to hear you are having problems.
Please create a new thread explaining the issue and including diagnostic logs as outlined at https://www.logos.com/support/logos5/mac/problem
Thanks, Graham
EDIT: I see you have started a new thread - http://community.logos.com/forums/t/87368.aspx - please reply to that thread including logs as outlined above
Just saw this thread reactivate this morning. Jonathan, were you able to solve your issue?
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
