Frequent crashes in Logos & Indexer after upgrade to Logos 5

Hi there,

I have recently upgraded to Logos 5 and have been having frequent crashes of the indexer and the application. I am currently at the point where the indexer has still not finished the first time index because it keeps crashing. Here are some example logs. Is anyone able to help out please?

thanks

Paul

2843.Logos Log Files.zip

Find more posts tagged with

Comments

TCBlack

Bradley Grainger indicated that it is not the indexer here.

Another similar problem was located with a specific Bible resource.

Do you have a copy of the indexer.log? That would indicate what was being indexed at the time of the crash.

Bradley Grainger (Logos)

The errors in your log are not common, and also don't seem to be very reproducible. (While the program is always crashing, it's never crashing in the same way twice.)

This makes me suspect that there's an underlying hardware problem that is causing random failures in Logos 5. The multi-core indexing of Logos 5 can sometimes stress inadequately-cooled hardware to breaking point.

One way to try to work around this is to force Logos 5 to only use a single indexing thread. This will dramatically slow it down, but may improve stability. (You could also blow out any dust from a desktop computer, or try using a laptop cooling stand for a notebook.)

To do this, copy the following line to the clipboard, then open a command prompt. Click the icon in the top left, then select Edit > Paste. (If necessary, press Enter.) It should say "The operation completed successfully."

reg add HKCU\Software\Logos4 /v MaxIndexingThreads /t REG_DWORD /d 1 /f

Try launching Logos 5 again. You should see much lower CPU usage in Task Manager, and hopefully it will finish indexing without error. (It will probably also pay to type "rebuild index" into your Logos 5 Command Box, to force the existing indexes to be recreated from scratch.)

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/419410#Comment_419410

Bradley Grainger indicated that it is not the indexer here.

While that post is a similar error message, the error details are different, and it is related to the indexer in this case.

Dave Hooton

https://community.logos.com/discussion/comment/419414#Comment_419414

Bradley Grainger indicated that it is not the indexer here.

While that post is a similar error message, the error details are different, and it is related to the indexer in this case.

You're right on it again! I was just about to post...

Paul M

https://community.logos.com/discussion/comment/419411#Comment_419411

Thanks for the note Bradley. Running on one core is indeed indexing much better. It has still crashed a few times however it is almost complete. I will let you know if I have any further issues.

thanks

Paul

Paul M

https://community.logos.com/discussion/comment/420699#Comment_420699

Just a quick update, indexing finished successfully with only one crash. However I am still getting Logos exiting without an error message at all. I have attached my log files again. Does this still point to a similar issue?0576.Logos Log Files.zip

Dave Hooton

https://community.logos.com/discussion/comment/421766#Comment_421766

However I am still getting Logos exiting without an error message at all.

Those show crashes but if Logos is exiting without giving a crash report we need to see a couple of instances of logos.log.