This has been reported on the Logos 5 Forum, but since I am on the Beta, started a new thread here. Took 2 process samples via Logos Logging Utility, then left L5 and Logging Utility run overnight. Now, both were frozen, and both needed Force Quit via Activity Monitor.
Here are the 2 samples from Logging Utility
5074.LogosLogs.jackcav.20130401-211114.zip
2627.LogosLogs.jackcav.20130401-211139.zip
Logos 5 Logs after Force Quit
6840.LogosLogs.jackcav.20130402-051905.zip
Sample of Logos Logging Utility from Activity Monitor during the Utility's freeze. Note that it was left on overnight prior to this freeze.
0247.Sample of Logos Logging Utility.txt
Made repeated attempts to attach Apple Crash Report, but the forum software would not accept it from Safari or from FireFox.
Upon restart of L5 received request to send Crash Report to Logos. Made the attempt, but received a dialog informing me that an error occurred in the transmission—Time Out.
However, so far, L5 seems to be operating normally. Quit and restarted L5 normally and received another request to send error report to Logos with the same Time Out error.
Enable-and-Submit-Log-Files | Install
Dear Jack,
I do not understand why it is so hard for a program to simply quit.
Son, Daniel, has tried to explain this to me. Guess it is not so simple to quit.
Christ is risen!
Ever in Christ,
David
Phil. 4:19
David Bergquist:Guess it is not so simple to quit.
Ain't that the truth. Glad I never took up smoking.
macOS, iOS & iPadOS | Logs | Install
alabama24: David Bergquist:Guess it is not so simple to quit. Ain't that the truth. Glad I never took up smoking.
Maybe force is simplest.
Just go directly to force quit in the first place.
About 1/3 of the time, I have to force quit. This is new to more recent builds.
Just tried going directly to force quit.
It worked really well, fast and clean.
So, is there any advantage to the regular quit
when it so often hangs ??
David Bergquist: is there any advantage to the regular quit when it so often hangs
is there any advantage to the regular quit
when it so often hangs
Sure. When you go through the normal shut down procedure, Logos has a checklist of things it attempts to do, including a quick sync and saving of your layout. If you go to <option> (force) quit, you bypass all of that. My guess is that this could potentially lead to things like corrupted databases, etc. (Ask Daniel and see if I'm right! )
I don't remember having much of a problem with shut down until I switched over to the 5.1 builds, but I could be wrong. In any case, it is worse now than before.
Neither Brisa, Kelly, nor I can recall having seen this behavior recently. I'll pass your logs on to Development to see if they can uncover the issue. Thanks Jack!
Diagnostic Logging