Crash on Logos 5 alpha 5, without crash report or log file error

Crash occurred with Set New Display to True.

I had navigated to several tabs, not yet open since updating to L5a5. Clicking on one of them (Continental Commentary, I think), crashed Logos and brought up the Windows error handling dialog. There was no error number, just "Checking for solutions to the problem" (or whatever that standard message is).

I'll post the logs, but they don't show anything discernible, as far as I can tell.

6663.Logos.log

6014.awesomium.log

(BTW, love the name "awesomium" Smile )

EDIT: Oops, accidentally posted the same log 2X. Deleted the redundant copy.

Find more posts tagged with

Comments

Rich DeRuiter

This crash appears to be repeatable. The particular resource is 2 Corinthians 8 and 9: A Commentary on Two Administrative Letters of the Aposlte Paul, (Hermeneia), by Hans Dieter Betz. The resource was opened to 2Corinthians 9:5, but navigated down about 7 paragraphs. That page, as is visibly displayed, appears to have Latin and Greek words (in addition to English, of course). The resource has no link sets enabled. The only check marks in the panel menu are "Show locator bar" and "Show footnotes on page."

Possibly relevant settings: Program Scaling = 100%. Default font = "Default." Default Text Size = 140%. Greek Font = Gentium Plus ; Greek Transliteration Format = SBL Greek. (Hebrew & Syriac settings considered irrelevant, if you want them, or other settings let me know.)

Crash does not occur with Set New Display to No. (which is how I got the above information.)

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/403565#Comment_403565

Thanks for the excellent bug report (you answered all the questions I had). I can reproduce the problem (and can write a fix), but I can't see a workaround other than disabling the new display.

It's related to Latin text, so you should be able to use resources that don't contain Latin with the new display.

Rich DeRuiter

https://community.logos.com/discussion/comment/403608#Comment_403608

Thanks for the excellent bug report (you answered all the questions I had). I can reproduce the problem (and can write a fix), but I can't see a workaround other than disabling the new display.

It's related to Latin text, so you should be able to use resources that don't contain Latin with the new display.

You're welcome.

It's interesting that Latin text would do this, since we use the same alphabet. I know, I know, it's a tagged language in the resource. Still, it seems odd that a display issue would be affected.