CRASH - When Closing Library Window

This is the second crash I have experienced today. The previous time
I was closing a guide window and the application quit. Recently, I
closed the Library window, and the application quit.

I am uploading the logging folder.

Since I am using the beta channel, this may be just a bug with this
iteration, but I figured I would post if anyone would find it helpful.

Thanks in advance.

4251.Logging.zip

Find more posts tagged with

Comments

Dave Hooton

The crash log may be helpful to Logos, but it would be better if you permanently enabled logging (being on the beta) so we could also get logos.log.

Jeff Terrell

https://community.logos.com/discussion/comment/450401#Comment_450401

Thanks Dave. I apologize, but I am unfamiliar with how to permanently enable logging and then extracting the logos.log file. Could you direct me?

Thanks.

Graham Criddle

https://community.logos.com/discussion/comment/450926#Comment_450926

Hi Jeff

I apologize, but I am unfamiliar with how to permanently enable logging and then extracting the logos.log file. Could you direct me?

No apology necessary

Details are at http://wiki.logos.com/Diagnostic_Logging

Graham

Jeff Terrell

https://community.logos.com/discussion/comment/450927#Comment_450927

Okay, so it just crashed again (after updating to the latest beta) when I was simply moving from one Scripture location to another within the ESV - the window is linked to several different resources.

I have posted the crash logs for that crash.

I also just followed the wiki for diagnostic logging. I can't remember if I had already done that. If not, this probably won't have what you were looking for. If so, I hope the log is in the compressed file. Thank you!

2744.Logging.zip

Tonya J Ross

https://community.logos.com/discussion/comment/452590#Comment_452590

Was there an Apple crash report for this crash? If so, it would be helpful if we you could post that as well (paste the details in a TextEdit document, for example).

Also, it doesn't look like you did have logging enabled at the time of this crash. Since you now have logging enabled, we would appreciate it if you could post new logs if you get this crash again.

That said, I will pass what you have posted on to Development for investigation.

Jack Caviness

https://community.logos.com/discussion/comment/452590#Comment_452590

I also just followed the wiki for diagnostic logging.

Jeff: For future reference

The most convenient way to enable logging is to use the Applescript LogosLogging by KS4J. (Restart of Logos needed after enabling)

Then use Logos Log Scribe to create an archive of the logs on your desktop.

Tom Philpot (Faithlife)

Jeff,

We've put in some crash reporting in the latest betas of 5.1 and I see that this error is still occurring for you with some frequency.

We've not be able to reproduce it internally and I'd like some more details about your Mac's setup. Do you have any third party apps that you use? My thought is that one or more of these apps (e.g. Moom, SizeUp) might be causing some problems.

Thanks,

Tom

Jeff Terrell

https://community.logos.com/discussion/comment/472701#Comment_472701

Tom,

Sorry I am just now seeing this. Yes, I continue to experience crashes. Mostly, this has begun once I have started putting my MBP to sleep rather than shutting it down.

As for third party apps. Only runs I have running in the background are PrinterProDesktop (allows me to print wirelessly from iOS devices), Covenant Eyes, LogMeIn, DropBox...that's all I can think of. Forgive me if I am missing the "third party apps" concept you are asking for...

Hope this helps.

Jeff

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/478199#Comment_478199

Jeff,

No worries. Thanks for responding. We're just trying to see if there is any common factors between the users who are experiencing the crash. The logs don't have much to go on. The crash in the logs happens deep within Apple's code. I suspect there is a latent bug in our code somewhere that doesn't trigger a crash immediately, but crashes later in a spot that is not directly related to where the bug actually is.

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/478199#Comment_478199

Jeff,

Besides resources like books, what other tools or documents do you normally have open in a layout when you sleep and resume your MBP? For example, Bible Sense Lexicon, Timelines, Text Comparison, Cited By, Notes, etc.

If we had a bit more information about what types of things you were doing before you put your Mac to sleep, we might be able to reproduce this internally.

Jeff Terrell

https://community.logos.com/discussion/comment/478215#Comment_478215

I have open pretty much all the guides (Passage, Topic, Sermon Starter, Exegetical) as well as Text Comparison and Info - along with books.

I found today that Logos5 clocked (spinning pinwheel) for about 15 minutes after I woke up the laptop. I forced it to quit, and it has been working fine since.

Hope this helps.

Jeff Terrell

https://community.logos.com/discussion/comment/478215#Comment_478215

I would expect there are plenty users with more resources open than mine, but I wonder if the volume of resources open at one time is contributing? (I am attaching a screen capture to give you an idea.)

2260.Screen.tiff

JT (alabama24)

https://community.logos.com/discussion/comment/478635#Comment_478635

I have open pretty much all the guides (Passage, Topic, Sermon Starter, Exegetical) as well as Text Comparison and Info - along with books

Wow. You have a LOT open. What are your computer specs?