I had previously supplied the key name = Holy Spirit and still it crashes.
1538.Logos4Crash_BibPeople.zip
I was able to duplicate this 'crash'. Biblical People opened with name Abraham and all was fine. I changed it to Holy Spirit and it crashed.
2043.Logos Log Files.zip
Restared Logso and it now opens with Holy Spirit due to it now being in the History and it crashes straight away
This is log files after the second crash:
7484.Logos Log Files.zip
Holy Spirit and still it crashes.
Confirmed
3731.Biblical People.zip
Note this is now causing biblical people to crash in my main user account where I have 4.0d SR2 installed. Even if I run a passage guide and open Biblical People to an entry different from HOLY SPIRIT it still crashes. When I switch back to main account I will turn on logging so I can get some logs to post for that install. May be a bit later today before I get to do that.
this crashes 4.0dSr2 and i have not been part of the beta in any way.
5417.Logos4 (20).zip
Edit: to get BP not to crash, i had to do:a) Restart L4b) In Genesis right click on Adam and select Person on the right and Biblical People on the left.c) This will crash the first time.d) Restart L4e) repeat step B, at this point it might work from the Tool menu.
I can reproduce this too. I was thinking maybe the crash fixes in 4.1 Beta 10 might have fixed it, but nope. It still crashes in B10.
Beta 10 installed before I switched back to my main account and at the moment it is now not crashing for me but 'good' to see some others have caught the crash and posted the logs. I've now got logging permanent on my main install so will be ready next time something like that happens. Got run ... some lecturers in half an hour
Yes, it was first reported here in 4.0d so I'm hoping it will be fixed in 4.1 beta (please, Melissa!).
My cure is to use Passage Guide and open Bib People to a name other than Holy Spirit. This resets the default when opening it from Tools menu.
It is distinct from the 4.1 beta crashes so I'm not surprised it still exists in B10.
Bump.
This will be fixed (for both 4.0d and 4.1) with a resource update; I'm not sure when that is scheduled to ship.
Good to know that. Thank you.
This is fixed as of the new release of Biblical Places database that downloaded today. I was running into it regularly, but I've confirmed it's fixed.
