Page 1 of 1 (3 items)
This post has 2 Replies | 0 Followers

Posts 9468
Forum MVP
Mark Smith | Forum Activity | Posted: Mon, Oct 29 2018 6:52 PM

Can't get L8 back up and running. This crash is repeatable.

1462.LogosCrash (2).zip

3108.LogosError (11).zip

Pastor, North Park Baptist Church

Bridgeport, CT USA

Posts 9060
LogosEmployee

This looks like the same crash that you reported earlier, which you said was “fixed” by rebooting your system. That may help again for this crash.

Are you opening to a blank layout? If not, does opening to a blank layout stop the crash?

A full Logos.log file would help (can you include that next time?), but it seems possible that this crash may be related to the Highlighting Tool. Does opening the Highlighting Tool seem to trigger the crash?

Posts 9468
Forum MVP
Mark Smith | Forum Activity | Replied: Mon, Oct 29 2018 7:56 PM

Bradley Grainger (Faithlife):

This looks like the same crash that you reported earlier, which you said was “fixed” by rebooting your system. That may help again for this crash.

Are you opening to a blank layout? If not, does opening to a blank layout stop the crash?

A full Logos.log file would help (can you include that next time?), but it seems possible that this crash may be related to the Highlighting Tool. Does opening the Highlighting Tool seem to trigger the crash?

More info: Yes it is just like the former crashes. 

I rebooted to no avail.

There is no log file generated. The program opens (I open to my last open layout), it does not populate the screen, hangs for a minute, then crashes. If I open to a blank layout it will crash as soon as I try to click on anything. My normal layout does have the highlighting palate open, but, of course, a blank layout doesn't.

One time you had me try deleting a fontcachexxxx.dat file. I tried that again. No love.

Since the error stack seems to refer to fonts, I though about the fact that I use a font manager called Extensis Suitcase. I decided to uninstall it. Rebooted, then tried again. This time no crash. Did this just a few minutes ago.

I'm going to leave the font manager uninstalled for awhile and see what happens. I noticed some funny things going on with my fonts on Google Chrome today, so perhaps Extensis Suitcase was messing up that as well. They are back to normal now that it is uninstalled.

While I hope that I've found the culprit, I do need that font manager, so I'll have to get something worked out.

Pastor, North Park Baptist Church

Bridgeport, CT USA

Page 1 of 1 (3 items) | RSS