Doesn't Mac have a Force Quit option through the top left dropdown box?
BUG: Logos refuses to leave the building
Jack Caviness
MVP Posts: 13,612 
Logos 8.13 Mac OS 10.15.4
Typed Cmd-Q to exit the application. More than 12 minutes later, Logos is till synchronizing. Exit Now ineffective. This is a recurring problem.
3632.Sample.LogosLogs.jackcav.20200501-163413.zip
1526.Activity Monitor Sample.rtf
0
Comments
-
Doesn't Mac have a Force Quit option through the top left dropdown box?
WIN 11 i7 9750H, RTX 2060, 16GB RAM, 1TB SSD | iPad Air 3
Verbum Max0 -
David Wanat said:
Doesn't Mac have a Force Quit option through the top left dropdown box?
It does, but I was giving Logos a chance to exit gracefully [:P] After compiling sample logs, I did force the app to quit.
0 -
Jack Caviness said:
Typed Cmd-Q to exit the application. More than 12 minutes later, Logos is till synchronizing. Exit Now ineffective. This is a recurring problem.
I have been having a similar issue. It's intermittent but reoccurs often enough to be annoying. I was about to post about it a few days ago, but then it stopped doing it so that I could gather a clean set of logs! Grrr.
This is what I was going to put in my post:
Whenever I try to quit Logos 8.12 on macOS 10.15.4, it stalls and refuses to completely quit. I have to right-click the icon in the dock in order to Force Quit it. It doesn’t matter if there is a layout active or not. I can start Logos with a blank layout and immediately try to quit it and have the issue occur.
All the windows close, but the “Synchronizing” pop-up stays in place. When I try to click on “Exit Now,” I get a beach-ball.
PS-I love the post title, Jack.
0 -
Levi Durfey said:
PS-I love the post title, Jack.
Credit Kelsey Grammer for that. I would sometimes watch Fraser. Each episode would end with "Fraser has left the building." But I probably misspelled the actor's name [:P] Looked it up and corrected my spelling.
0 -
Levi Durfey said:
I have been having a similar issue. It's intermittent but reoccurs often enough to be annoying. I was about to post about it a few days ago, but then it stopped doing it so that I could gather a clean set of logs! Grrr.
Ok, now it's doing it again. Here are my logs:
A sample taken while it was hung:
7167.LogosLogs.Levi.20200503-084507.Sample.zip
Full logs:
0 -
I experience similar issues:
https://community.logos.com/forums/p/190012/1098459.aspx#1098459
0 -
Bump for Faithlife
Dave
===Windows 11 & Android 13
0 -
it would be great if Faithlife could look into these logs and provide a fix.
0 -
Jack Caviness said:
Logos 8.13 Mac OS 10.15.4
Typed Cmd-Q to exit the application. More than 12 minutes later, Logos is till synchronizing. Exit Now ineffective. This is a recurring problem.
3632.Sample.LogosLogs.jackcav.20200501-163413.zip
1526.Activity Monitor Sample.rtf
Hi Jack,
We've got a bug report and I added a link to this thread.
0 -
Many thanks, Philana. My samples and logs are here:
0 -
0
-
0
-
Sorry, I spoke too early. I still have issues when closing down Logos. Even when using it, the Sync icon often displays the "!".
0 -
Philana R. Crouch said:
We've got a bug report and I added a link to this thread.
Hi Philana,
I still have issues. Do you know when a likely fix will become available?
Armin
0 -
In case somebody else has this issue, here is a workaround that works for me most of the time: I need to close all tabs and windows, wait a bit, and then shut down Logos. This way, it closes down most of the time without hanging.
0 -
Armin said:
I still have issues. Do you know when a likely fix will become available?
Since the issue in the OP of this thread has been resolved, you probably need to start a new thred in order to get attention concerning your issue.
0 -
Jack Caviness said:
Since the issue in the OP of this thread has been resolved, you probably need to start a new thred in order to get attention concerning your issue.
Hi Jack, Is the issue resolved for you? I still have the same problem described in the original post.
0 -
Armin said:
Hi Jack, Is the issue resolved for you? I still have the same problem described in the original post.
As far as I can tell, it's fixed for me
0
