Logos Keeps Crashing On Start Up
2425.LogosError.logLogs attached.2821.LogosCrash.txt
Comments
-
It would help to enable logging and upload the compressed log files folder.
Dave
===Windows 11 & Android 13
0 -
Looks like it is a problem with a profile.
Got around this using <ctrl> on startup
Work Offline
If I load my last shutdown profile Logos crashes.
More important things to do right now that debug this.
0 -
Graham Owen said:
Looks like it is a problem with a profile.
Got around this using <ctrl> on startup
Work Offline
If I load my last shutdown profile Logos crashes.
More important things to do right now that debug this.
Graham,
Once you are able to get us logs please post them here so we can take a look.
Thanks,
Philana
0 -
Philana R. Crouch said:
Once you are able to get us logs please post them here so we can take a look.
Thanks,
Philana
Thanks Philana
It looks like as long as I don't open my old layout I am OK. I have only tried the last two versions so I'm not sure when the corruption or bug occurred. Support have suggested a reinstall which I am reluctant to do as every time I have done this in the past it takes me days to get everything sorted out.
My plan is to recreate my layout rather than try and reload the ones that are crashing Logos as this seems like the quickest route to getting back to normal.
Frustrating thing is that because Logos does not seem to remember that the last startup failed it took a while and a couple of reboots to get a system up and running. Having an easily accessible "safe mode" would really have helped.
Took me over an hour to start Logos to do my daily reading, not the best advert for software efficiency.
0 -
Graham Owen said:
Having an easily accessible "safe mode" would really have helped.
Something other than opening to a blank layout? I assume that is what you did to get back in?
Graham Owen said:Support have suggested a reinstall which I am reluctant to do as every time I have done this in the past it takes me days to get everything sorted out.
This is curious advice. If their suggestion was simply to reinstall the engine, that is very simple and would not lead to "days sorting things out." If they meant a complete wipe, that would be a long process... but if the layout was the problem, it would have been redownloaded in its corrupt state and would have been an utter waste of your time. Sounds like bum advice to me. I wonder what their thinking was.
0 -
Hi Alabama
Maybe reinstalling is a viable option these days. I'm speaking from memory because in the past when I did a reinstall things took a while to sort out.
Sounds like the reinstall they are suggesting will act more like a repair in which case it might be worth a go.
What is really confusing is that I have gone back a full week and my close layout from every day causes Logos to crash.
0 -
Here are logs from a clean (ctrl) start then an open of the layout that is failing.4807.LogosError.zip
0 -
Graham Owen said:
Maybe reinstalling is a viable option these days. I'm speaking from memory because in the past when I did a reinstall things took a while to sort out.
Two things can be meant by a "reinstall." The most basic is a reinstall of the software engine, but most of the time there isn't a reason to do that (by itself). This leaves all resources, indices, notes, etc. in place... those things are kept elsewhere. The reason that doing a reinstall of the software engine by itself is pointless (most of the time) is for that very reason. Frequently crashes are caused by a corrupt index. Deleting and reinstalling the software engine doesn't fix that. If there is a "bug" in the current release, then deleting and reinstalling is also pointless (until a fix is pushed out) since you will be installing the same bug again.
The second type of "reinstall" is where you wipe everything, including data files. That DOES take a while and leads to having a long indexing session and downloading of resources (unless you use a backup method).
0 -
Graham Owen said:
Frustrating thing is that because Logos does not seem to remember that the last startup failed it took a while and a couple of reboots to get a system up and running.
It loads the the last "safe" layout after a crash but the dynamic elements of a panel could be responsible e.g. things that changed with a resource before the crash.
Graham Owen said:It looks like as long as I don't open my old layout I am OK.
The log file indicates the crash comes from a search panel for NASB95. If you can't load an older version of the layout without error then it is best to reconstruct it without using NASB95. If you subsequently get a crash opening/searching NASB95 then create a new thread with logs.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
If you can't load an older version of the layout without error then it is best to reconstruct it without using NASB95.
So this is crazy as the first thing that I did when I opened to a clean layout is open the NASB95, which is my Bible of choice, without problems.
Given that I went back a week there are at least 7 saved layouts on my system created at shutdown that Logos has successfully opened but which now cause a crash. My conclusion here is that the latest update introduced this problem.
0 -
BTW - is there an easy way to rollback to the previous version update?
0 -
Graham Owen said:
BTW - is there an easy way to rollback to the previous version update?
Sorry, no.
Graham Owen said:My conclusion here is that the latest update introduced this problem.
If that is true, the issue should be reproducible by someone else.
0 -
alabama24 said:Graham Owen said:
My conclusion here is that the latest update introduced this problem.
If that is true, the issue should be reproducible by someone else.
In theory yes, the challenge being that with sophisticated data driven software like Logos the permutations of use cases tends to infinity!
Hopefully the logs will reveal something to the developers.
0 -
Graham Owen said:
Given that I went back a week there are at least 7 saved layouts on my system created at shutdown that Logos has successfully opened but which now cause a crash. My conclusion here is that the latest update introduced this problem.
I don't have a problem opening my saved layouts.
Graham Owen said:Dave Hooton said:If you can't load an older version of the layout without error then it is best to reconstruct it without using NASB95.
So this is crazy as the first thing that I did when I opened to a clean layout is open the NASB95, which is my Bible of choice, without problems.
Try to recreate the layout with NASB95 and see if you can reproduce the problem.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Try to recreate the layout with NASB95 and see if you can reproduce the problem.
I have many saved layouts that work Dave
The point is that either at least 7 days of my ever evolving "shutdown" layout have become corrupted or the update that automatically downloaded immediately prior to the error has a bug. The logs might suggest that the NASB95 is the issue but based on the way it fails I think that the new courses view is the more likely candidate.
I already have a new version of my "layout" working with the NASB95. Recreating what I have lost is not that easy I use the "shutdown" layout as a way of picking up my thinking from the day before so its not a static layout that I can easily recreate. Whilst I would have liked to get a back when I first reported the problem the reality for me now is that it is lost. Of course as my layout evolves the error might reoccur at which point the suspect list will be a lot smaller.
0 -
This is the same problem as I just responded to here. I think you need to avoid having a Search Panel and Bible Browser in your layout at the same time until we get a release with the bug fix. Sorry for all the trouble.
EDIT: I was wrong. Your crash is different, but I'll take a look at it too.
EDIT2: It turns out I was wrong and I was right. It looks like you've been affected by both crashes, so my earlier advice also applies.
EDIT3: I got to the bottom of it. The two crashes were caused by the same code, so my fix works for both. Essentially the one crash happened when the search was run and Bible Browser didn't have resource text, and the other happened when it did have resource text.Unfortunately this means until the service release with the fix is ready you can't use Bible Browser at the same time as a search.
0 -
Lawrence Rafferty said:
Unfortunately this means until the service release with the fix is ready you can't use Bible Browser at the same time as a search.
Thanks Lawrence
0 -
Graham Owen said:
2425.LogosError.logLogs attached.2821.LogosCrash.txt
This should be fixed by 7.2 SR-1
0 -
Philana R. Crouch said:Graham Owen said:
2425.LogosError.logLogs attached.2821.LogosCrash.txt
This should be fixed by 7.2 SR-1
Fixed by today's update, thanks.
0 -
0
