lbs 4 crashes

I have a problem with lbs 4, when I open Passage guide fx matt 1:1 and toggle around, and then open ESV with interlinear, then it crashes, and only then, otherwise not. I hope it is understandable with my poor english.

I have Win 7 64-bit.

Can anyone help me ?

Find more posts tagged with

Comments

Dave Hooton

Jack,

We need to see some logs when Logos4 crashes. See http://wiki.logos.com/Diagnostic_Logging, but wait a minute after the crash before closing L4. Collect and zip the log before starting L4 again.

Rosie Perera

I have a problem with lbs 4, when I open Passage guide fx matt 1:1 and toggle around, and then open ESV with interlinear, then it crashes, and only then, otherwise not. I hope it is understandable with my poor english.

I have Win 7 64-bit.

Can anyone help me ?

Jack, your English is perfectly understandable. Could you be more specific about what steps you took? What do you mean when you toggle around? What exactly did you click on? Then, how did you open the ESV with interlinear? For example, did you type ESV on the command bar, or click to open it from a verse reference somewhere in the Passage guide? (Is ESV set up as your default Bible?) Was the interlinear already turned on in ESV from the last time you had opened it, or did you click on "Interlinear" to open it just before the crash? Any extra details like this which you could provide would be helpful in seeing if anyone else can reproduce this bug. Pretend you're giving instructions to someone else to produce exactly the same result you got. And does it happen every time for you when you do these steps? I tried to replicate approximately what you were talking about, but it didn't crash for me.

There might also be some unique configuration on your machine which is the culprit. The log files will be helpful for Logos in debugging the problem.

Thanks!

Jack Nørdam

https://community.logos.com/discussion/comment/56819#Comment_56819

I'll try to be more specific next time it happens, and I think that will be soon. If I can find out that log-thing, then I will send that one too.

Jack Nørdam

https://community.logos.com/discussion/comment/57023#Comment_57023

It crashed again, and now I have a log file. After the crash it just closed down, I could not do anything, but then as I started LBS4 again, I hold down the CTRL key, and the result is attached - I hope it is done correctly.2437.Logos4.log

Jack Nørdam

https://community.logos.com/discussion/comment/56819#Comment_56819

Jack, your English is perfectly understandable. Could you be more specific about what steps you took? What do you mean when you toggle around? What exactly did you click on? Then, how did you open the ESV with interlinear? For example, did you type ESV on the command bar, or click to open it from a verse reference somewhere in the Passage guide? (Is ESV set up as your default Bible?) Was the interlinear already turned on in ESV from the last time you had opened it, or did you click on "Interlinear" to open it just before the crash? Any extra details like this which you could provide would be helpful in seeing if anyone else can reproduce this bug. Pretend you're giving instructions to someone else to produce exactly the same result you got. And does it happen every time for you when you do these steps? I tried to replicate approximately what you were talking about, but it didn't crash for me.

There might also be some unique configuration on your machine which is the culprit. The log files will be helpful for Logos in debugging the problem.

Thanks!

In detail I just do the following thing: I open Passage Guide "matt 1:1" and then it opens all my books, also the prefered bibels, one of them is ESV with interlinear 'on' (if you know what I mean), it is number two. So I click on the ESV-tab. Then it opens. As soon after it opened as I point with the mouse on one greek word in the ESV interlinear it crashes.

It is complicated for me to explain it correctly, because I feel I need some more tecnical words, that I do not have, but I try the best I can.

Dave Hooton

https://community.logos.com/discussion/comment/57051#Comment_57051

We need the log file before you start L4 again, because it is overwritten each time you start L4. Wait a minute after the crash, rename the log file and then you can start L4!

George Allakhverdyan

https://community.logos.com/discussion/comment/57055#Comment_57055

Jack, your English is perfectly understandable. Could you be more specific about what steps you took? What do you mean when you toggle around? What exactly did you click on? Then, how did you open the ESV with interlinear? For example, did you type ESV on the command bar, or click to open it from a verse reference somewhere in the Passage guide? (Is ESV set up as your default Bible?) Was the interlinear already turned on in ESV from the last time you had opened it, or did you click on "Interlinear" to open it just before the crash? Any extra details like this which you could provide would be helpful in seeing if anyone else can reproduce this bug. Pretend you're giving instructions to someone else to produce exactly the same result you got. And does it happen every time for you when you do these steps? I tried to replicate approximately what you were talking about, but it didn't crash for me.

There might also be some unique configuration on your machine which is the culprit. The log files will be helpful for Logos in debugging the problem.

Thanks!

In detail I just do the following thing: I open Passage Guide "matt 1:1" and then it opens all my books, also the prefered bibels, one of them is ESV with interlinear 'on' (if you know what I mean), it is number two. So I click on the ESV-tab. Then it opens. As soon after it opened as I point with the mouse on one greek word in the ESV interlinear it crashes.

It is complicated for me to explain it correctly, because I feel I need some more tecnical words, that I do not have, but I try the best I can.

Hi Jack, thanks for the steps and yes it makes perfect sense what is going on, but Dave is correct, the Log file is overwritten every time you launch logos4, so it is best to rename the log file after the crash before restarting Logos 4 and attach that file here.

Jack Nørdam

https://community.logos.com/discussion/comment/57105#Comment_57105

We need the log file before you start L4 again, because it is overwritten each time you start L4. Wait a minute after the crash, rename the log file and then you can start L4!

I do understand you, but when it crashes it also close down. Then it is closed - how can I then make a log file?

Jack Nørdam

https://community.logos.com/discussion/comment/57177#Comment_57177

Maybe I managed to do anyway - is this right? 5482.renamed Logos4.log

George Allakhverdyan

https://community.logos.com/discussion/comment/57185#Comment_57185

Maybe I managed to do anyway - is this right? 5482.renamed Logos4.log

It worked perfect this time, thanks. I can't really read the error though, which language is it in? Can you provide a rough translation of this:

Indekset lå uden for området. Det må ikke være negativt og skal være mindre end størrelsen på samlingen.

Thanks.

Edit:
Google Tools helped me translate this, for reference it is: Index was outside the area. It must not be negative and must be less than the size of the collection.

Thanks Jack, I have reported this error and will get back to you when I find out what we can do to move forward.

George Allakhverdyan

https://community.logos.com/discussion/comment/57185#Comment_57185

Maybe I managed to do anyway - is this right? 5482.renamed Logos4.log

A fix for this issue will be included in 4.0a, which will be released in about 1-2 weeks. In the mean time the only way around it is to not open the reverse interlinear for that verse in ESV which is causing the crash.

Jack Nørdam

https://community.logos.com/discussion/comment/57326#Comment_57326

thanks for the help - and bugs or not, lbs4 is still a fantastic biblesoftware, so I hear your advice and read some of all the other books

Rosie Perera

https://community.logos.com/discussion/comment/57213#Comment_57213

Maybe I managed to do anyway - is this right? 5482.renamed Logos4.log

It worked perfect this time, thanks. I can't really read the error though, which language is it in? Can you provide a rough translation of this:

Indekset lå uden for området. Det må ikke være negativt og skal være mindre end størrelsen på samlingen.

Thanks.

Edit:
Google Tools helped me translate this, for reference it is: Index was outside the area. It must not be negative and must be less than the size of the collection.

Hey, that's impressive! Logos logging error messages have already been translated into Norwegian for the Norwegian version. ;-)

Jack Nørdam

https://community.logos.com/discussion/comment/57475#Comment_57475

No, no - this is danish