The big hang for me is that I broke my ankle on Sunday.
It is not very easy to plug my computer directly into the modem.
WiFi is so nice from my lounge chair with my leg up.
WiFi seems to work fine for everything else.
I am healing and am so blessed.
Ever in Christ,
David
Phil. 4:19
If you remember to hit the sync button before you quit Logos 5 you should be fine.
Shutdown performance is tied to the network? As a software developer myself, that seems like a Bad Idea®.
If it is really necessary to sync data over the network at shutdown, there should at least be a progress bar and a cancel button if it's taking too long. This sort of thing should never prevent this sort of app from exiting quickly, much less beachball.
12-Core Mac Pro, MacBook 2.0 GHz Core Duo, Mac mini
Favorites: http://www.piratechristianradio.com http://issuesetc.org
This is a new problem.
i have never had this issue until the update that came out this week.
I see the same exact thing you are describing.
How do we let Logos know about this problem?
Tim, Logos reads this forum. They may very well already know about the issue.
I had hope that Logos would cleanly quit on Paul Sunday,
but I must need to continue with this little cross.
I just synced Logos, then tried to quit.
Logos hung again, became unresponsive
and I had to force quit Logos.
Offline is the reliable way to get a Logos clean quit.
Another cross I continue with is spelling.
I of course mean Palm Sunday.
David, can you post logs of you syncing then after it finishes closing the app?
Tommy,
Do I use "Sample" or "archive logs" after it hangs,
but before I force quit Logos ?
Thanks!!
So is the order:
sync
quit
hang
"sample" or "archive logs" ??
force quit
Hit Sample in the step you have it in, and after the sample is taken force quit, then archive logs.
This hang happened after the MacBook Pro was closed for the night.
Sync seemed to work.
2538.LogosLogs.davidbergquist.20130326-100856.zip
4745.LogosLogs.davidbergquist.20130326-100703.zip
Logos 5 is running better with RAM up to 16 gigs since Saturday
Woke this Monday morning, opened MacBook with Logos still running from the night before.Tried to quit Logos after several minutes of working with other programs.Logos was not responding and had to force quit.
I did not sync before I tried to quit, thinking it is not needed with the incresed RAM.
Attached are the Logs:
8880.LogosLogs.davidbergquist.20130401-093059.zip
6786.LogosLogs.davidbergquist.20130401-093456.zip
This time I did sync Logos before I tried to quit Logos.Again Logos came up in the force quit box as not responding.After several minutes I forced quit Logos
1385.LogosLogs.davidbergquist.20130401-171010.zip
5127.LogosLogs.davidbergquist.20130401-171229.zip
Experienced hang on quit with both L5 Beta 3 and the Logos Logging Utility. Reported here on the Beta forum 5.1 Beta 3 Mac Freeze on Quit
Enable-and-Submit-Log-Files | Install
David, Just to confirm, you saw the sync arrows stop moving prior to shutting down Logos and made no further actions in the application after they stopped spinning and prior to attempting to shut the app down?
This is exactly what I did and what happened.
Christ is risen!!!
Opened MacBook
Yesterday Logos quit fine several times.
Early today this happened:
Checked weather conditions and forecast
Closed Safari
Synced Logos, went to Home page and synced Logos again, arrows stopped
Tried to close Logos with only the System Monitor running
Sample, force quit, log
5123.LogosLogs.davidbergquist.20130404-044534.zip
5078.LogosLogs.davidbergquist.20130404-044617.zip