Crash: New Moody Atlas of the Bible

Lee

Just ordered New Moody Atlas of the Bible.

For some reason, when I access this resource and click around (a map for example) Logos 5 crashes unexpectedly.

Platform: Windows 8.1 x64. All updates applied. Worked perfectly before.

Log attached (edited for privacy).7028.Logos.log

Find more posts tagged with

Comments

Floyd Johnson

For some reason, when I access this resource and click around (a map for example) Logos 5 crashes unexpectedly.

Platform: Windows 8.1 x64. All updates applied. Worked perfectly before.

I have a similar configuration for my system (Lenova ThinkPad Twist) and am seeing no problem with this resource.

Dave Hooton

For some reason, when I access this resource and click around (a map for example) Logos 5 crashes unexpectedly.

Is LLS:9781575673721 the resource in question (paste into the Command box to find out), because there is no crash info? If there is no crash log (LogosCrash.txt) for the time it happened, then look in Windows Event viewer and paste relevant information from it.

Lee

https://community.logos.com/discussion/comment/569027#Comment_569027

The resource in question is indeed LLS:9781575673721.

Two events were triggered in Event Viewer:

Event 1026, .NET Runtime

Event 1000, Application Error

The only thing that strikes me as odd is the line in the Event 1026

LDLS4.OurApp.InitializeAndRun(System.Collections.ObjectModel.ReadOnlyCollection`1<System.String>,Libronix.Utility.Threading.SingleInstanceManager)

Lee

https://community.logos.com/discussion/comment/569094#Comment_569094

Strangely enough, I do not crash the program until I click around within this passage:

Name shifts may also occur from one culture or period of time to another. Old Testament Rabbah became New Testament Philadelphia, which in turn became modern Amman. Old Testament Acco became New Testament Ptolemais, which in turn became Acre to the Crusaders. Old Testament Shechem became New Testament Neapolis, which evolved into modern Nablus. And in some instances a name change occurred within a Testament (e.g., Luz/Bethel, Kiraith-Arba/Hebron, Kiriath-sepher/Debir, and Laish/Dan). Analysis of these cases often demands an intimate familiarity with the cultural succession and linguistic interrelationships between several epochs of Palestinian history. Even then, site identification often remains elusive.

Beitzel, B.J., 2009. The new moody atlas of the bible, Chicago, IL: Moody Publishers.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/569094#Comment_569094

Your first Pastebin includes the text "OnMouseWheel". Are you using the mouse wheel to scroll, or are you clicking? (Or does it crash for both?)

I found the article you cited (starting with "Name shifts", logosres:9781575673721;art=r10.a42;off=877;ctx=,_and_elsewhere.142$0A~Name_shifts_may_also) but couldn't reproduce a crash when clicking in and around that paragraph.

Lee

https://community.logos.com/discussion/comment/569242#Comment_569242

Clicked. What would you recommend, a "rebuild index" maybe?

Dave Hooton

https://community.logos.com/discussion/comment/569282#Comment_569282

I would hide the resource, then restart Logos to see if the resources was corrupt.

Then rebuild library index may be worth a go (it saves rebuilding the Bible index).

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/569287#Comment_569287

Then rebuild library index may be worth a go (it saves rebuilding the Bible index).

I suspect that wouldn't be helpful in this case. The one crash log that was posted indicates a problem with the resource display (and mouse interaction), which isn't affected by the library index (but really only by the resource file itself, so if that is corrupt, hiding/unhiding to download a new copy, as you suggested, is probably the best course of action).

Lee

https://community.logos.com/discussion/comment/569357#Comment_569357

I don't have an explanation for this.

Hid and unhid the resource so it was downloaded again. A corrupt resource download is out of the question. Clicked around the paragraph and its environs, and got the crash again. Am I really the only one seeing this? [:(]

Dave Hooton

https://community.logos.com/discussion/comment/569483#Comment_569483

If you can, try a different mouse. Otherwise get in touch with Tech Support who can connect to your computer and diagnose the issue.

Lee

https://community.logos.com/discussion/comment/569575#Comment_569575

Thanks, Dave and Bradley. I don't really have the time to do deeper troubleshooting. Maybe I'll just return the resource.