Bug: Crash while opening a reading plan.

Lynden O. Williams

Selected the passage for a reading plan (I am behind) and the software crashed.

4186.Crash.zip

Find more posts tagged with

Comments

Philana R. Crouch

Selected the passage for a reading plan (I am behind) and the software crashed.

4186.Crash.zip

Lynden,

These logs don't have any data related to the crash. It shows a normal shutdown. When this occurs again could you save the log files right away and upload them?

Thanks,

Philana

Philana R. Crouch

Selected the passage for a reading plan (I am behind) and the software crashed.

Lynden,

I wasn't able to reproduce this. Which Bible translation were you using and did you select if from a reading plan on the Homepage or was it open in a layout?

Blessings,

Philana

Lynden O. Williams

https://community.logos.com/discussion/comment/825247#Comment_825247

I wasn't able to reproduce this. Which Bible translation were you using and did you select if from a reading plan on the Homepage or was it open in a layout?

Opened the software (my login had been in sleep mode since Saturday night) Opened the software and clicked the passage the app crashed.

I did upload the logs as soon as the crash before restarting the app.

Lynden O. Williams

https://community.logos.com/discussion/comment/825273#Comment_825273

Philana, I should mention that there was a exclamation mark (red I think) in the sync area.

Clicked on the passage from the home page and the app crashed.

4034.LogosCrash.zip

Lynden O. Williams

https://community.logos.com/discussion/comment/825275#Comment_825275

Cleared the log folder, restarted the app, selected the text I wanted to read from the home page, and (red sync mark still there) and the app crashes.

5100.LogosCrash.zip

Lynden O. Williams

https://community.logos.com/discussion/comment/825277#Comment_825277

Cold boot, started the app (sync is back) selected the passage I wanted to read from the Reading plan on the home page, and app crashes.

1616.LogosCrash.zip

JT (alabama24)

https://community.logos.com/discussion/comment/825282#Comment_825282

Lynden - You don't appear to have logging enabled.

Lynden O. Williams

https://community.logos.com/discussion/comment/825333#Comment_825333

Don't know when it was disabled, but I have re-enabled it.

Lynden O. Williams

https://community.logos.com/discussion/comment/825340#Comment_825340

Here it is with diagnostic logging enabled.

3324.LogosError.zip

JT (alabama24)

https://community.logos.com/discussion/comment/825348#Comment_825348

Here it is with diagnostic logging enabled.

Several things:

You must have logging enabled if you want to provide logs. It would be best to leave it on since you are asked to provide them regularly.
You must grab the logs AFTER the crash but BEFORE you reopen Logos. There is no crash in your logos.log file. You do have a crash log, but your logos.log file (the one really needed) indicates that you reopened logos before grabbing the logs. That isn't helpful and defeats the purpose of providing logs since opening up Logos overwrites the needed log with a new one once the application starts!
When you are using beta, you MUST post in the beta forum so that the right people will see your log files.

Lynden O. Williams

https://community.logos.com/discussion/comment/825383#Comment_825383

Thanks alabama.

I did post logs after the crash and before reopening.

Lets try it again.

456756.Logos.log

2630.LogosCrash.txt

2605.LogosError.log

JT (alabama24)

https://community.logos.com/discussion/comment/825387#Comment_825387

I did post logs after the crash and before reopening.

...but according to the logs, you didn't.

Crash Log: 2016-06-07 07:21:23
Logos Log: 2016-06-07 07:24:44.5690

Your Logos Log shows Logos opening three minutes AFTER the crash log was generated.

I can't be of any more help with how to generate the logs since I (thankfully) don't have to use windows. [;)]

Lynden O. Williams

https://community.logos.com/discussion/comment/825413#Comment_825413

I can't be of any more help with how to generate the logs since I (thankfully) don't have to use windows.

Don't feel left out. Mac use is on the increase, (heard it is the largest single brand being sold, especially with college kids) which means they along with criminals will be searching for vulnerabilities, to exploit the software.

Philana R. Crouch

https://community.logos.com/discussion/comment/825387#Comment_825387

Lyden,

Even though I couldn't reproduce this on my machine, I uploaded your logs and created a case.

Philana R. Crouch

https://community.logos.com/discussion/comment/825387#Comment_825387

Thanks alabama.

I did post logs after the crash and before reopening.

Lets try it again.

456756.Logos.log

2630.LogosCrash.txt

2605.LogosError.log

Lynden, Like Alabama said logging is not turned on. Can you double check that you are following the steps found https://www.logos.com/support/logos6/windows/report-problem and try to get us logs again? Thanks, Philana

Lynden O. Williams

https://community.logos.com/discussion/comment/825445#Comment_825445

Was using the old method of diagnostic logging in the wiki. Was not aware of this new method you suggested Philana.

Here is the new method.

2742.LogosError.log

2742.Logos.log

5481.LogosCrash.txt