Crash on passage guide 7.1 beta 3

Program version: 7.1 Beta 2 (7.1.0.0008)

Also in program version: 7.1 Beta 3 (7.1.0.0010)

Bug:

Logos is crashing - noticeably after loading a default passage guide layout.Description:

At the moment I'm trying to run a "type in the passage and click go" on Luke 22:35-38. Every time it loads it crashes. I did just attempt to start with a blank layout and load just a passage guide. It is also crashing as the passage guide generates.
Dialog Box text: The only dialog box is the crash notification.

Steps to reproduce:
Easy: Either run a passage guide, or start the layout from the home page using your passage.

System Specs:

Laptop | Windows 10 | Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz | 8GB RAM | Four Monitors: (HP L1740=1280X1024), Dual 22" widescreen monitors vertical at 1050x1680, Built in 1600X900| ATI Mobility Radeon HD 4670 |500 GB HD/ 200GB free |

Find more posts tagged with

Comments

Philana R. Crouch

Hey TCBlack,

So it looks like you have a corrupt resource that is causing you to crash. Make sure Logos is not running. Then locate your Resources folder.

If you can go to your Resources folder, the path will look like:

C:\Users\Philana\AppData\Local\Logos\Data\demo_5574347\ResourceManager\Resources and sort these by date.

You can move the specific resources that downloaded near the time you saw the crash to a different location. Then restart Logos and they should download. Only delete the specific files, not the folder.

Let me know if this fixes the crash.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/848373#Comment_848373

You may have a corrupt resource. Before you start deleting files, I'd like you try some searches to narrow down the problem. Do any of these searches (Basic Search in All Resources) crash?

<Thing Bag>
<Thing Sword>
<Thing Sandal>

If so, does searching just Bibles still crash? What about searching non-Bibles? ("* -type:bible")

At this point, looking at recently-updated resources and searching just within them may show if it's actually a corrupt resource or something else.

TCBlack

https://community.logos.com/discussion/comment/848373#Comment_848373

Makes sense, there were a number of resources from today that all had a date stamp right around the time a power failure hit here.

I'm happy to report that this appears to have fixed it.

[y]

TCBlack

https://community.logos.com/discussion/comment/848468#Comment_848468

Sorry Bradley, I did the delete last night.