Crash: L5.1b SR-2 (5.1.2.0083)
Repeatable crash on my state-of-the-(old)-art Lenovo T61. Follow steps A to C as described by Morris Proctor's blog post. L5 crashes before step D.
Also, Windows 7 allows me to send crash information to Microsoft! Just a suggestion to Logos - could you provide built-in transmission of crash data from our computers directly to Logos?
Logs in zipped folder
David
Comments
-
It looks like it is crashing in the Passages section. You could try generating a Sermon Starter without that section (or with it minimised). Also check database versions in Help >> About Logos... in the scrolling section on the left:-
Sermon Starter Guide
DB:PREACHINGTHEMES
2013-09-06T15:47:15Z
DB:THEMATIC-OUTLINES
2013-02-22T17:48:51ZDave
===Windows 11 & Android 13
0 -
Hi Dave,
Yes, the crash occurs while the Passages section is calculating. I have not used Passages section and the Sermon Starter Guide (SSG) in months; so, I can't point to a past time when L5 crashes due to the items mentioned. I do have the latest db:
L5 crashes on two PCs whenever I use the default Sermon Starter Guide (SSG). I created a custom SSG with just Passages section. L5 crashes. I created a second custom SSG without the Passages section. L5 does not crash. I then add the Passages section to this second SSG and L5 does not crash. Edit: But then L5 crashes when I re-open and use this customized SSG with Passages section.
I then noticed that my default SSG no longer has the Passages section (I did not expect this because I thought L5 makes a copy of the customized Guide, not change the default?). I added Passages section back to the default SSG and L5 crashes.
As you had mentioned earlier, Dave, it looks like the issue is Passages section.
thanks,
David
0 -
Exactly the same crash occurred for another user about a month ago: http://community.logos.com/forums/t/74939.aspx
It resolved itself after a bit of fiddling, but no-one was really sure why! Perhaps you could take a look at that thread and see if it helps.
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 -
Exactly the same crash occurred for another user about a month ago: http://community.logos.com/forums/t/74939.aspx
It resolved itself after a bit of fiddling, but no-one was really sure why! Perhaps you could take a look at that thread and see if it helps.
Thank you Mark. You must have a very good memory and forum search skills. [:)] I will remove Passages section from my default SSG until I hear back from Logos.
David
0 -
David,
I am the person who had the same problem about a month ago. Check your preferred Bible and make sure that you have an English translation at the top of your priority list for Bibles. If it is any other language such as Greek or Hebrew, it seems to crash. The SSG uses the English translations to build it's database. Let us know what happens.
Blessings
James Bills
0 -
David,
I am the person who had the same problem about a month ago. Check your preferred Bible and make sure that you have an English translation at the top of your priority list for Bibles. If it is any other language such as Greek or Hebrew, it seems to crash. The SSG uses the English translations to build it's database. Let us know what happens.
Blessings
James Bills
Thank you James. I will take a further look into this. Currently, my prioritization looks like this. Note that my top two Bibles are NLT and NIV, and they are setup with the advanced conditions:
David
0 -
David,
I will try to reproduce your problem on my system in a few minutes. I will get back with you soon.
James
0 -
Thank you James. I will take a further look into this. Currently, my prioritization looks like this. Note that my top two Bibles are NLT and NIV, and they are setup with the advanced conditions:
Hi David, I've reproduced the crash by having my most highly prioritised Bible restricted to the Old Testament. That fits with the scenario on the other thread when James had his most highly prioritised Bible restricted to the New Testament. Hopefully, the programmers will be able to fix that bug in version 5.2.
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 -
David,
I will try to reproduce your problem on my system in a few minutes. I will get back with you soon.
James
After I made the NASB95 my top prioritized english bible, and added Passages section back to the default SSG, and search a topic such as "Prophecy: Jesus", I don't experience crashes.
I placed NASB95 back to a lower level and made NLT and NIV my top two bibles with advanced conditions. L5 then crashes. What are your results, James?
David
0 -
Hi David, I've reproduced the crash by having my most highly prioritised Bible restricted to the Old Testament.
Wonderful Crash! I mean, thank you Mark for validating the crash and narrowing down the possible cause(s). [Y]
David
0 -
David,
I too was able to reproduce the crash when I placed a restriction on my top prioritized Bibles to the OT. I guess you know what to do from here.
God's Blessings
James
0 -
David,
I too was able to reproduce the crash when I placed a restriction on my top prioritized Bibles to the OT. I guess you know what to do from here.
God's Blessings
James
Thanks James for validating the crash condition.
David
0 -
I am able to reproduce this crash on Mac in 5.1b SR-2, and I have created a case for Development.
0 -
This crash will be fixed in 5.2 Beta 2.
0 -
This crash will be fixed in 5.2 Beta 2.
Thank you Angela!
0
