First-load crash, consistent behavior.

Ben said:

Whenever I load L4 after it being closed for some time, the main
screen doesn't appear and one must force-quit the program.

This was happening to me several weeks ago. I discovered that I could make everything appear by selecting "Preferences" from the Logos menu. I thought this had been fixed in 4.2a.

Randall Cue said:

Jack what did you do when you selected "Preferences" from the Logos menu? What if anything did you change there?

I just closed the window. Everything else appeared when the Preferences window appeared. Your problem may have a different cause.

It would help if you would post your log files. See the first link in my signature for instructions. The second link describes LogosLogScribe, a superb utility that automates the gathering process and places a compressed archive on your desktop.

Randall Cue said:

I'll post the logs the next time this behavior appears.

I should mention. Post the logs before you restart Logos as a restart will overwrite previous logs.

Jack Caviness said:

Randall Cue said:

Jack and anyone else who might help, here are my logs.

I can't discern much from logs, but others can. If one of them does not respond to this thread by tomorrow, I will make sure KS4J sees them. I am a bit surprised that he has not posted yet.

Logs not have any crash information, but look similar to initial set of logs after my 4.2a SR-3 upgrade.  Logos4.log file has "IndexerProcess | Indexer process ID is ####; watching for exit.", but has nothing after Indexer.log posts "IndexerProgram | Shutting down services."  Also, suspect Activity Monitor shows Logos Bible Software 4 is not responding, so force quit needed, followed by relaunching program.

Ben said:

Whenever I load L4 after it being closed for some time, the main screen doesn't appear and one must force-quit the program. Reloading it right after works fine. This has happened repeatedly for the last several days, at least. 

Likewise Logs not have any crash information.  Logos4.log file has "IndexerProcess | Indexer process ID is ####; watching for exit.", does have many lines after Indexer.log posted "IndexerProgram | Shutting down services." including an ERROR "FormatException for saved text range:" - did notice Logos 4.log time entries for 31 seconds after Indexer.log posted completion.

Puzzled by force quit needed on 3 different Mac computers. [:^)]

Keep Smiling [:)]

Jack Caviness said:

" rel="nofollow">Keep Smiling 4 Jesus said:

Puzzled by force quit needed on 3 different Mac computers

Thanks for checking. Maybe we need to get the Dev Team's attention.

Concur, especially since couple initial launch hangs are running 4.2a SR-3 stable release (released earlier today) - suspect process communication issue related to Indexer completion.

Keep Smiling [:)]