Crash & other fun stuff (5.1b6 Mac)

I had several things out of the ordinary, so I thought I would upload logs.

At least twice during this session, new resources were downloaded and indexed without a restart occurring.
After one of the downloads, the indexer kind of half started (blank indicator) for a seemingly long time. I waited for a while to see if it would indeed start indexing and it did… but it was long enough that I almost decided to force close it before it did.
After the last download & indexing cycle, I closed the app down via the menu. It crashed during the shut down procedure. This is a semi-regular occurrence.

Here are my logs. I have also included the crash log produced by apple, just in case it is helpful. I pasted it into a .docx file. (Is there a better way to do that?)

0131.LogosLogs.20130502-190113.zip

Apple Logs: 1055.Apple Logs.docx

Find more posts tagged with

Comments

Tom Philpot (Faithlife)

alabama24,

Here are my logs. I have also included the crash log produced by apple, just in case it is helpful. I pasted it into a .docx file. (Is there a better way to do that?)

During the 5.1 beta cycle we've been collecting crash reports when the app restarts. If you have diagnostic logging enabled (which you do) and you've been submitting the reports, we should have the logs on the crash in our crash reporting database. We made a change in Betas 5 and 6 on the Mac to prevent some of the crashes on shutdown based on some of the reports we've collected.

The crash you're experiencing also manifests when quitting, but is not related to the crash on quit we fixed in Betas 5 and 6. I did notice in the logs you posted that the app was running for over 24 hours when you finally quit. Is that your typical usage pattern? When you've had the app running for a long time does it regularly crash on quit?

We're trying to find a common pattern that will help us reproduce the crash in-house. If you have any other data, I'd love to hear it.

JT (alabama24)

https://community.logos.com/discussion/comment/485762#Comment_485762

During the 5.1 beta cycle we've been collecting crash reports when the app restarts.

Everytime the app asks if I want to report, I tell it yes… but every time I have paid attention (until yesterday), the self report has failed. I believe I created a thread about that somewhere…

I did notice in the logs you posted that the app was running for over 24 hours when you finally quit. Is that your typical usage pattern?

Kind of. I normally let Logos run most of the time. Normally, Logos will restart when new resources are downloaded. I pick up freebies and cheap vyrso titles most days, which means Logos restarts most days. (By the way, can you address the download and indexing without a restart?)

When you've had the app running for a long time does it regularly crash on quit?

I will try to keep an eye out for a pattern. The 5.1 build have certainly been much more prone to crash on quit for me.

JT (alabama24)

https://community.logos.com/discussion/comment/485785#Comment_485785

I did not experience a crash after closing Logos 3-4 times after performing simple tasks.

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/485785#Comment_485785

(By the way, can you address the download and indexing without a restart?)

Here's a summary of what I'm able to reconstruct from the logs:

You started Logos 5 5/01 at about 11 PM.
Your licenses were updated twice between when the app started and when the app shutdown.
The first time the licenses were updated, the indexer started up and downloaded the new resources automatically and requested they be installed next time the app restarts
Licenses were updated again later, and the indexer again started up and downloaded the new resources.
This time though, the indexer mistakenly thought Logos 5 had shut down, when it was in fact still running. Because if this it started to discover and index the resources. (This is the "weirdness"; normally this should not happen until the app is restarted or quit while the indexer is running).
Finally, Logos 5 was shut down on 5/02 at about 7 PM.

Why the "weirdness" happened is something I'll have to look into.

JT (alabama24)

https://community.logos.com/discussion/comment/485876#Comment_485876

Thanks Tom. I have been interested for a long while why the app sometimes doesn't prompt a restart during updating. For a while I thought perhaps only small downloads might cause this, but have since found that not to be the case.

JT (alabama24)

https://community.logos.com/discussion/comment/485889#Comment_485889

Here are some new logs:

8880.LogosLogs.20130504-132939.zip

fgh

https://community.logos.com/discussion/comment/485889#Comment_485889

I have been interested for a long while why the app sometimes doesn't prompt a restart during updating.

I don't know if this helps, but I can't remember this ever happening to me. Perhaps because I'm on 10.6? (EDIT: Because it's not a beta issue, is it? I think I've seen you complain about it on stable as well?)

Jack, you're on 10.7, aren't you? Has it happened to you?

JT (alabama24)

https://community.logos.com/discussion/comment/486482#Comment_486482

Because it's not a beta issue, is it?

It has been happening every now and then for at least a year.

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/486482#Comment_486482

I don't know if this helps, but I can't remember this ever happening to me. Perhaps because I'm on 10.6? (EDIT: Because it's not a beta issue, is it? I think I've seen you complain about it on stable as well?)

Jack, you're on 10.7, aren't you? Has it happened to you?

My current thought is that it's a bug in the Mono runtime that could affect all versions of Logos 5 (and possibly Logos 4) on all Mac OS X versions and unrelated to the 5.1 betas. I don't know the root cause and haven't been able to reproduce the bug in development yet, although I know exactly where the problem occurs and how the bug manifests itself.

I'm hoping to spend some time looking in to the bug this week. Fortunately, we have all the source code for Mono, so it's a simple matter of reading the code, writing some test code to reproduce the bug, fixing the code, testing the fix and repeating until we squash the bug.

David Bailey

https://community.logos.com/discussion/comment/486533#Comment_486533

I just downloaded an update base package and did not have to re-start. What I do to save CPU resources is close out Logos 5 as it downloads the files. As long as the Logos icon is visible in the task/notification bar, I am good to go. The software does not prompt me to re-start; it goes straight to indexing phase (which I don't mind). I am using Windows 7 Pro 64-bit on my state-of-the-old-art Lenovo T61.

David

JT (alabama24)

https://community.logos.com/discussion/comment/486533#Comment_486533

Here are some new logs, from my iMac this time: 6403.LogosLogs.20130506-155304.zip

JT (alabama24)

https://community.logos.com/discussion/comment/486628#Comment_486628

After a download (I think it was preaching themes), I was prompted for a restart. I clicked to do so, and after a minute or so, this popped up:

I restarted the app, and everything appeared to be good. I used quit from the Logos menu, but was forced to use a force quit after a few minutes. Here are the logs: 1374.LogosLogs.20130506-210218.zip

Jon

https://community.logos.com/discussion/comment/486533#Comment_486533

My current thought is that it's a bug in the Mono runtime

If it's possible for Logos to keep running while stuff is updating in the background, why require a restart?

A second possibly related issue, this morning logos updated it self without restarting; I paused indexing and after some time put my mac to sleep, when it awoke from sleep it automatically started indexing again long before 4 hours had passed. In the logs it says "'Resume indexing' context menu command was invoked." however comparing the timestamp of that entry against my system log, that fired as soon as the computer woke from sleep before I'd even logged in...

2474.Logs.zip

Jack Caviness

https://community.logos.com/discussion/comment/487397#Comment_487397

started indexing again long before 4 hours had passed.

Have noticed this previously when using an MBP, but thought it might be a feature rather than a bug—If this is intended behavior, it is not a good choice [:(]