Bug: Crash when building Morph Visual Filter

I was clicking to the morph visual filter screen and Logos crashed. Attached are my logs. I hope someone from development looks at these because I don't have time to telephone in.

70725.Archive.zip

EDIT: After posting these logs, I went to restart Logos again to resume my studies and it crashed again on startup even before the opening screen! Here's another set of logs.

426142.Archive.zip

Find more posts tagged with

Comments

Jack Caviness

Donovan

Cannot duplicate your crash. What steps did you follow prior to the first crash?

Donovan R. Palmer

Hi Jack - nice to see you online... it's been awhile!

I was in the Bible Visual filter screen, started filling out my criteria, realized I was in the wrong screen and clicked on the morph visual button and then boom... and crash. No explanation and I have no clue why that would crash it. Unfortunately, all of my crashes of late have no pattern or explanation! [:(]

Keep Smiling 4 Jesus :)

Unfortunately, all of my crashes of late have no pattern or explanation!

Wonder if have a bootable partition with Snow Leopard ? (vis OS X Lion)

Keep Smiling [:)]

Donovan R. Palmer

All I got is Lion and a standard factory install. In fact, I am a minimalist and install very little software on my computer because I don't like clutter.

Keep Smiling 4 Jesus :)

I was clicking to the morph visual filter screen and Logos crashed. Attached are my logs. I hope someone from development looks at these because I don't have time to telephone in.

Noticed Logos4.log has several "ERROR | 17 | RichTextUriLink | Uri is not valid: " and couple messages: "ERROR: value [NSConcreteMutableAttributedString] is not a kind of IEnumerableOfRichTextElement" in file before crash of Native Notify Property Changed.

Noticed Visual Filter editing is syncing while being built and modified.

EDIT: After posting these logs, I went to restart Logos again to resume my studies and it crashed again on startup even before the opening screen! Here's another set of logs.

Memory Allocation error for 4 GB again.

Wonder about restarting Mac, then work offline to build Visual Filter ?

Keep Smiling [:)]

Donovan R. Palmer

Yes, I noticed these errors as well. I did reboot and I built the visual filter with no problem. That being said, I should not have to reboot to make my computer run Logos. I'm not on the beta channel. This is full release software. NO OTHER software package on my computer runs this way... this is one of the reasons why I went Mac.

Thanks for your help anyhow. I am going to do the persistent widow thing because from now on, any crashes I have I am going to post my logs on here. I won't stop until the crashing stops.

Jack Caviness

I should not have to reboot to make my computer run Logos.

Unfortunately, L4 Mac does have some Windows-like features. The need to reboot seems to be one of them. I remember the good old days (2008) when it was not necessary to reboot a Mac for months [:D]

Tom Philpot (Faithlife)

Donovan,

The crash at startup seems to be related to an issue with Lion and the window theme we use for the Login window. I understood that we had a solution to the problem in 4.3 in SR-2 or 3, but there still seems to be problem. I'll have to forward this on to the Logos 4 Mac guys for investigation. (I'm working on Proclaim these days).

The other crash seems to be a bug in the Mac Morph Reference Builder. Both the logs point to where the problem lies so we'll just have to create bugs for both of these issues.

Donovan R. Palmer

Hi Tom - many thanks for the response and explanation. It's good to know that the logs can specifically pinpoint the problem.

Tell Bob to put a little extra something in your Christmas stocking!... and maybe I might be praying you get reassigned to Logos 4 Mac again? [;)] (nothing against Proclaim, just selfish)

Donovan R. Palmer

Unfortunately, L4 Mac does have some Windows-like features. The need to reboot seems to be one of them. I remember the good old days (2008) when it was not necessary to reboot a Mac for months

I had a very, very bad week with this Jack. I used to accept this years ago, but this was why I went to OSX. I was sick of software that wouldn't stay up and running... I do hope this is the blip in the road because as much as I would like to see feature parity, I would rather a program with less features that is stable than a full feature program that crashes unpredictably and even loses data (as I found this week) The strength of this in another Bible program that you and I own really shown this week!

Tom Philpot (Faithlife)

I understood that we had a solution to the problem in 4.3 in SR-2 or 3, but there still seems to be problem.

Double checked with some of the other Mac developers and the crash at startup bug fixed in SR-3 was a different issue, not related to the one you're experiencing Donovan. It's still an issue in SR-6.