Logos crashes when waking up with no internet/wi-fi

Whenever I am at home on wi-fi and close my Macbook Pro with Logos running and go somewhere without wi-fi/internet and resume (or wakeup), Logos hangs up and crashes consistently within a few minutes. The operation I perform to cause the hang is random but it's usually when I go to the passage box on a bible to change verses. My assumption is that it was signed in and no longer can access the internet and something is depending on it for syncing, etc. When I open it again in offline mode, it seems stable.

88775.Archive.zip

Find more posts tagged with

Comments

Donovan R. Palmer

Yup, I can confirm this. Logos is not very robust and seems to not like it when the connection changes or disconnects because you are on the fringe.

Fr. Charles R. Matheny

https://community.logos.com/discussion/comment/382486#Comment_382486

Same Issue here.

Thomas Ball

HI Matt,

Can you change the layout you are at before you close the lid on your computer, and repeat the steps you described to cause Logos 4 to crash and post the Logs? I want to compare them to the originals. I'm not sure, but I am doubtful that WiFi is the problem here. I think the issue may be more along the lines of how Logso 4 is handling coming back from the computer being asleep.

Thank you.

Matt Chroninger

https://community.logos.com/discussion/comment/382537#Comment_382537

Sorry I haven't checked back in a while. I didn't realize I didn't check the "email me when..." option.

For a while it seemed that simply starting Logos when resuming and working offline resolved the issue but tonight it happened several times. When I travel I switch the my integrated graphics to save on battery and fairly consistently when I typed in a passage to a linked resource (such as my ESV which is linked in group A to quite a few panels), I could see it start drawing that yellow diamond (for the current passage locator) and trying to update my passage guide before it locks up. I force closed 5 times and it happened every time. Finally I just started using a non-linked ESV I keep open along with everything. I'm beginning to wonder if there are areas of my many panels (such as the passage guide) that rely heavily on internet. I've attached the recent logs.

Next Tuesday I will be in the same situation again and can try it. What kind of layout would you recommend switching to? I realize I have many resources open but while I have internet accessibility it is very speedy and reliable but acts like a 10-year PC when not. I also want to get the steps down to make sure I give you the log you want:

1. Be on layout A
2. Switch to layout B <--- what should this look like?
3. Close lid

8666.Archive2.zip

Thomas Ball

https://community.logos.com/discussion/comment/390247#Comment_390247

For a while it seemed that simply starting Logos when resuming and working offline resolved the issue but tonight it happened several times. When I travel I switch the my integrated graphics to save on battery and fairly consistently when I typed in a passage to a linked resource (such as my ESV which is linked in group A to quite a few panels), I could see it start drawing that yellow diamond (for the current passage locator) and trying to update my passage guide before it locks up.

Does this happen only when you force Logos 4 to use the Intel HD graphics? Believe it or not there is a decent amount of memory being used on the display end to pull all that off. To reproduce the behavior with regards to the internet, can you try mimicking it by opening L4, turning your WiFi off on the computer, and close the lid and re-open it? Would that reproduce the issue, or would you have to go from L4 having internet, to closed lid, to being opened again somewhere with no internet?

Matt Chroninger

https://community.logos.com/discussion/comment/390701#Comment_390701

Last Friday I kept my graphics on the discrete GPU and turned off my wi-fi, closed the lid, later opened it and had no issues. Tuesday I kept it on discrete with wi-fi on, went somewhere without internet, opened the lid, used L4 for a few passages lookups with no problem, switched to the Integrated GPU and still had no issues. I tried network monitoring (via Little Snitch) and didn't see any attempts for traffic (though maybe it won't report if it knows there's no connection).

I'll reply again once I replicate the issue again.

Matt Chroninger

https://community.logos.com/discussion/comment/392794#Comment_392794

Last Tuesday it crashed again, had the integrated graphics on before I closed the lid - a few minutes into using L4 and typing a passage in, it crashed. It appears something is trying to contact faithlife.com (the L4 log shows an attempt to use what is probably a web service at https://api.faithlife.com/community/v1/notes/destinations?resource=exdctbibnm&resourceVersion=2009-10-26T23%3A53%3A02Z and can't handle the situation properly when it's not available: Name Resolution failure or HTTP GET failure). What I assume is the main log also has communication errors to usereventsapi.logos.com while in its GetHasCurrentLicensesWork routine - perhaps something in there isn't safely handling the condition.

-Matt5226.Archive3.zip

Thomas Ball

https://community.logos.com/discussion/comment/399082#Comment_399082

Hi Matt,

I'm sorry the issue is persisting. Can you try a couple of things for me?

1. Re-install the application file. (delete from applications folder, and re-download from www.logos.com/mac).

If that doesn't work please sequester the logs, along with crash log that apple creates, and label it so that I know it was after you re-installed the application file.. You can copy and paste the text from the crash file into a textedit file.

2.) If the above does not resolve the issue, please try to power-cycle your router.

As before, if this too doesn't resolve the issue, sequester the logs with the Crash log Apple provides, and label them.

If neither step resolves the issue, post them here as you have been in the past. Thank you.

Matt Chroninger

https://community.logos.com/discussion/comment/399431#Comment_399431

I reinstalled the application and it worked fine that week. Last Tuesday I had the same lockup - this time when clicking into the passage box to type a new verse reference in. The attached archive contains the L4 logs and the crash log (using textedit to save as RTF).

6740.Archive-PostReInstall.zip

LimJK

https://community.logos.com/discussion/comment/407897#Comment_407897

Matt + Tommy,

Not sure if the following information is useful or relevant in your case, as you did not mentioned how you actually switch your graphics mode.

For me, I am using gfxCardStatus 2.3, and I have got some issues when I started using Mountain Lion, and since then I have always leave it in "dynamic switching mode" after I read the following:

http://gfx.io/switching.html#power-source-based-switching

Quote: For simplicity's sake, it's best to stay on Dynamic Switching, and use gfxCardStatus as a purely informational tool to tell you when apps are affecting your battery life.

I have not been using Logos for Mac for a while, I run Logos on Parallels. Just try it when I see this post, I noticed that the current version of Logos no more switch on the Discrete GPU like in the earlier versions.

Maybe crash may not be due to Logos [:)]

Before you close your lid, take a look at gfxCardStatus to see which application is in the dependency list, that may possibly be the culprit:

Thomas Ball

https://community.logos.com/discussion/comment/407897#Comment_407897

Hi Matt,

There does seem to be a good amount of sync errors prior to Logos' "final gasp" as it were. It would logically seem that the issue is related to Logos 4 trying to sync when opening offline from sleep. I'll do some investigating on my end, and if I need more information I think I may email you.

Thomas Ball

https://community.logos.com/discussion/comment/408474#Comment_408474

Hi Matt,

Development know what is going on. In the meantime if you turn off "visual cues" in the program settings, that should prevent the crash occurring under the circumstances you are experiencing it.

Matt Chroninger

https://community.logos.com/discussion/comment/409171#Comment_409171

Sounds good - I'll give that try next Tuesday! Thanks for the vigilance in tracking this down. I never got it to crash at home on integrated graphics so I assumed it was wi-fi but I look forward to testing this.