nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

4.5b Beta 5: Crash on "rebuild index"

Rosie Perera

I had recently updated some newly downloaded resources and updated to Beta 5. Indexing was completed.

I tried to reproduce this bug http://community.logos.com/forums/t/47231.aspx to see if it had been fixed in Beta 5.

Oddly, the search described in that bug report (chart WITHIN 2 words sacrifices) did not find any hits in the NLT Study Bible, the subject of my earlier crash report.

So I tried a search for just israel in that resource and it found nothing.

Figured it must be a bad index problem, so I entered the command rebuild index and hit Enter.

Got a crash in the Indexer right away. See screenshot and logs. There was no new Logos4IndexerCrash.txt from today. I'm attaching all the logs that had dates of today.

0317.Crash20120320.zip

Find more posts tagged with

Comments

Tonya J Ross

I will pass your logs onto Development for investigation.

Tonya J Ross

https://community.logos.com/discussion/comment/352822#Comment_352822

The looks like the crash is being caused by the file for AFHEB10.logos4 which may have become corrupted or unreadable for some reason. You may have issues opening that resource in the app. You might try deleting that file and redownloading/indexing it to see if that resolves the issue.

Rosie Perera

https://community.logos.com/discussion/comment/353117#Comment_353117

The looks like the crash is being caused by the file for AFHEB10.logos4 which may have become corrupted or unreadable for some reason. You may have issues opening that resource in the app. You might try deleting that file and redownloading/indexing it to see if that resolves the issue.

I had no problem opening that file in Logos.

Rebuild index seems to be working fine for me now, so I'm not sure what the problem was. But it's still troubling to me that there might be intermittent crashes lurking around that nobody can track down. Perhaps points to the need for more diagnostics in the log files.