Crashes whenever I close my Macbook Pro

Hello!

I have had Logos for about 3 years now and it crashes on me every time I shut my laptop with it running. As a Bible college student I like to have the programs I use running during the day for quick access, but I cannot open Logos without first force quitting the already frozen window which I previously opened. I have gotten so used to it I just assume its frozen every time I come back to my computer.

I have completely uninstalled it before and reinstalled it with no change.

Thank you!

Find more posts tagged with

Comments

Lee

I quote Jack from another thread:

Do you allow your MBA to sleep with Logos open? There is currently a bug with wake from sleep in the Mac version which is to be fixed in 5.2a. The fix will be tested in the upcoming beta and then incorporated in the stable release.

Dave Hooton

I think this diagnosis applies to your problem, but to be sure please attach logs as described at http://www.logos.com/maclogs.

PS please Edit (on the More button) your post and remove the Mac logging info which is not useful for Logos problems.

Curtis Bell

https://community.logos.com/discussion/comment/550863#Comment_550863

Thanks for replying, Lee and David. I'm sorry about that crazy long error report. I thought it would only show a link to the pdf. My bad. Also, If a Mac error report is not useful is there anything I can provide which is?

I do not quite understand you quote from Jack. My laptop does sleep and operate normally when logos is running except that when I return logos is frozen.

Curtis Bell

https://community.logos.com/discussion/comment/550869#Comment_550869

And I am in the process of trying what you sent me, Dave. I will let you know if it works or not soon.

Lee

https://community.logos.com/discussion/comment/550869#Comment_550869

My laptop does sleep and operate normally when logos is running except that when I return logos is frozen.

It's waking from sleep that's the problem. See this thread: http://community.logos.com/forums/p/78218/547017.aspx#547017

Dave Hooton

https://community.logos.com/discussion/comment/550869#Comment_550869

If a Mac error report is not useful is there anything I can provide which is?

My previous post has a link for getting Logos diagnostic logs!

Curtis Bell

https://community.logos.com/discussion/comment/550876#Comment_550876

If a Mac error report is not useful is there anything I can provide which is?

My previous post has a link for getting Logos diagnostic logs!

hahhaha! I am feeling like quite the "new guy" right now. Sorry, I better understood your message after I responded.

Here are the logs. Hopefully I did them right ;]

That does look like that is likely my problem Lee.

Thanks for the help and patience you guys.

1512.LogosLogs.Curtis.20131210-232650.zip

Dave Hooton

https://community.logos.com/discussion/comment/550880#Comment_550880

The crash info appears to be different to the case I cited. Logos will need to comment.

Dylan Rondeau

https://community.logos.com/discussion/comment/550880#Comment_550880

Here are the logs. Hopefully I did them right ;]

You did, but since you mention the app is frozen when you open the computer, I'd like to get a sample before making a case for this. Next time this happens, if you're using the Logos Logging application press the "Sample" button while Logos is still open and frozen. If you don't use the logging app:

Leave Logos open and frozen
Open Activity Monitor (type "activity monitor" in Spotlight, the magnifying glass in the top-right)
Click on the Logos Bible Software 5 process
Click the "Sample process" button

In either case, please upload the sample file here, or email it to LogosBugs@logos.com and mention this thread. Having the sample file is vital in diagnosing freezes/hangs.

Curtis Bell

https://community.logos.com/discussion/comment/551604#Comment_551604

Hey Dylan! I believe I dis everything you told me to do.

Hope it helps.

5670.LogosLogs.Curtis.20131213-181434.zip

Dylan Rondeau

https://community.logos.com/discussion/comment/551744#Comment_551744

Hi Curtis, a couple things I noticed:

You are still running 5.2 SR 1, the most recent version is SR 3. I doubt it'll solve the problem, but it would be good to update.
I think the big issue is this "Mutex not owned" error from Dec. 9th in your LogosError.log, but that didn't occur in the two sets of logs you posted.

I'd recommend updating to 5.2 SR 3, and then keep taking samples and posting them here in the hopes that we'll get one with the Mutex error. In the meantime, I've created a case for your issue in the hopes that your current logs/sample will turn up something.