L4 rc1? Crash

Dale Durnell, Retired UM Clergy
Dale Durnell, Retired UM Clergy Member Posts: 173
edited November 20 in English Forum

With all my time at the hospital with my wife, apparently I never got B9. But, I just found an update to L4 without a version number. I'm going to assume (terrible thing to do) that this might be RC1 -- but there's notihing to confirm this for me -- the Help About screen is silent on the issue

Just after running the update, I opened L4 -- checked to see what version, noticed that I'm still trying to get this 1.6 gb update downloaded, I got a crash notice (can't tell if it's the same one I reported last night as I'm now running a different version of the application)

Blessings,

Dale Durnell

Coming to you from Henryetta Oklahoma (45 miles south of Tulsa, and 85 miles east of OKC)

 

Tagged:

Comments

  • George Allakhverdyan
    George Allakhverdyan Member Posts: 1,075 ✭✭✭

    With all my time at the hospital with my wife, apparently I never got B9. But, I just found an update to L4 without a version number. I'm going to assume (terrible thing to do) that this might be RC1 -- but there's notihing to confirm this for me -- the Help About screen is silent on the issue

    Just after running the update, I opened L4 -- checked to see what version, noticed that I'm still trying to get this 1.6 gb update downloaded, I got a crash notice (can't tell if it's the same one I reported last night as I'm now running a different version of the application)


    Hi looking at the logs it seems like it was downloading an update and closed down the program in order to do the update. But you mention this happened after the update? The Logos4.log doesn't show the RC1 version number (version 4.0.3.2019), did it close L4 after the crash?

  • Dale Durnell, Retired UM Clergy
    Dale Durnell, Retired UM Clergy Member Posts: 173
    https://community.logos.com/discussion/comment/22004#Comment_22004

    Hi looking at the logs it seems like it was downloading an update and closed down the program in order to do the update. But you mention this happened after the update? The Logos4.log doesn't show the RC1 version number (version 4.0.3.2019), did it close L4 after the crash?


    Hi George --

     That's the strange thing about this crash -- *NOTHING* closed. L4 stayed open. The download continued. Indexing appears to have continued. BUT, I got a nasty "this program has crashed" type box on my screen saying that it would send the data to Microsoft. I clicked OK, let the crash reporting continue, and then sent my report. But, again, nothing closed.

    Blessings,

    Dale Durnell

    Coming to you from Henryetta Oklahoma (45 miles south of Tulsa, and 85 miles east of OKC)

     

  • George Allakhverdyan
    George Allakhverdyan Member Posts: 1,075 ✭✭✭
    https://community.logos.com/discussion/comment/22036#Comment_22036

    Hi looking at the logs it seems like it was downloading an update and closed down the program in order to do the update. But you mention this happened after the update? The Logos4.log doesn't show the RC1 version number (version 4.0.3.2019), did it close L4 after the crash?


     

    Hi George --

     That's the strange thing about this crash -- *NOTHING* closed. L4 stayed open. The download continued. Indexing appears to have continued. BUT, I got a nasty "this program has crashed" type box on my screen saying that it would send the data to Microsoft. I clicked OK, let the crash reporting continue, and then sent my report. But, again, nothing closed.


    Ahh that is expected! The problem here is the indexer was encountering a problematic resource and the result is a supposed crash, however the indexer keeps running. I think in the future releases we are planning to have the indexer silently step over problematic resources.

Categories