Crashes in Logos 4
Well, my worst nightmare is happening. I have the Scholar version and for the last week I have been really happy with Logos 4. Until now.
I have been using it on both my desktop and my laptop with not a single incident. Now it's crashing when I open a Layout. Crashing when I use Collections. I don't know what to do at this point. Customer Support says 24-48 for a reply, but I can't use it now on my desktop at all.
Thanks for any help.
Larry.
Comments
-
Larry, we will need diagnostic logs to look at. You can find out how to turn logging on permanently here: http://wiki.logos.com/Diagnostic_Logging
Once you enable diagnostic logging, allow the system to crash and locate the files in your My Documents folder, zip them into a single folder and attach them to a follow-up message here using the paperclip icon in the compose message panel.
You are most likely dealing with a corrupt database file or resource and the log files can help us isolate that.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
0
-
I think I did it wrong the first time, so here is another zip with a good crash.
0 -
Larry, it seems the crash is occurring when Logos is trying to do something with the ESV Reverse Interlinear. I'd suggest as a first step that we delete the ESV text to force Logos 4 to re-download it.
You can do this one of two ways:
1. Within Logos 4, open Program Settings and click on the Hidden Resources section at the bottom of the pane. Drag the ESV from Library to that area and drop it there. Now close Logos 4 and reopen it. This should cause Logos to delete the file. Once you verify that the file is gone from Library, reopen Program Settings and reverse what you did previously, dragging the ESV from there to Library and dropping it. Close and reopen Logos 4. That should trigger a re-download.
Note: to get around the current crash I'd try opening Logos by using the CTRL key work-around. Hold the CTRL key while you open Logos 4. Keep holding the key until you see a log-in screen. Select the open to a blank layout option and log in normally.
2. Go directly to the Logos 4 resources file and delete the ESV text. There are two of them with the file ending .lbsrvi. When you reopen Logos 4 it should detect the missing files and re-download them.
If you can get into Logos using the CTRL key option that is the method I'd use.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Do you mean the esvot.lbsrvi and esvnt.lbsrvi files in the Resources directory?
0 -
Larry Parker said:
Do you mean the esvot.lbsrvi and esvnt.lbsrvi files in the Resources directory?
I'm not Mark, but the way I read his instructions, yes, delete those two files.
Prov. 15:23
0 -
Kevin Becker said:
I'm not Mark, but the way I read his instructions, yes, delete those two files.
Those would be the ones as Kevin said.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
OK. It's indexing now. I will put it through the wringer and see what happens.
Why would this happen other than a bug in the software? Makes me leery that what I do will cause this to happen again soon.
0 -
Larry Parker said:
Why would this happen other than a bug in the software?
Larry, I doubt it is anything you have done. This is the first time I've seen that particular error and we don't know if we've properly identified the problem and fixed it yet. However, Logos 4 is more prone to these issues than any previous version of Logos was. When Logos can identify that something they've done is at fault, they fix it. When one person has a problem and others do not, then it points away from the software to other factors. Once we are sure what the problem is we might know better if Logos 4 is at fault.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
I understand that reasoning. I've been a beta tester for games and now am a tester for SwordSearcher Bible so this makes plenty of sense. I was hoping I was not the first, but on the other hand I wish no crashes on others. I realize if I'm the only one, then my system will be under scrutiny next.
Last night when I logged off of my desktop, I noticed when I went to my laptop that the last saved layout did not transfer. So going back to my desktop, every time I went to open that layout, it crashed. I was using the Interlinear a lot when I saved that layout.
When it's done indexing, I will give it a good test. Thank you for your fast help. That means a lot. I very much appreciate your time. God bless! [:D]
0 -
Are you using a custom guide (i.e., based on your own guide template) in the layout you're trying to load?
0 -
Bradley Grainger said:
Are you using a custom guide (i.e., based on your own guide template) in the layout you're trying to load?
Yes, I do.
I had saved my old layout database and just renamed it to try it again. The layouts still crash Logos. The same custom guide that's in those is in the new layout and the new one loads fine. I don't yet understand much about how Logos works so bear with me please. I'm trying to figure out why this happened so it won't ruin my bible studying in the future like it did today. [:@]
My laptop is entirely different from my desktop. One runs Vista and the other XP. The same two layouts that crash my desktop also crash my laptop, so it's probably not platform specific. I just wonder how those two layouts got corrupted... [:S]
0 -
Well, it seemed to be fixed, and I made a new layout last night and opened it this morning and it worked fine. Then I reopened it a few minutes ago this afternoon and things are acting weird again. I hated to do this, but I asked for a refund. I don't have the time or patience right now to chase bugs in a program that I need to be using.
Thanks for everyone's help.
0 -
This is now reported as fixed in 4.2a beta 6: http://wiki.logos.com/Logos_4.2a_Beta_6
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I ended up installing Win7 64 on one desktop and buying another desktop with Win7 64 on it. Now Logos runs wonderful! I'm so thankful some kind users in another thread talked me into sticking with it longer. [Y]
0
