Crash whilst doing nothing

I'd been using L5 quite a bit, but then switched to a web browser to go online. A couple of minutes later, Logos crashed, for no obvious reason. I'm afraid I didn't have full logging turned on as I've reinstalled my OS a few days ago.

Program Version: 5.0 SR-2 (5.0.0.1803)
Windows Version: 6.2.9200.0
Time: 2012-11-01 22:58:37 +00:00 (2012-11-01T22:58:37Z)
Installed memory: 6,143 MB
Install path: \Logos5\System\Logos.exe
Free install space: 101,171 MB
Data path: \Logos5\Data\5yknfsfa.x3n
Free disk space: 101,171 MB
Temp path: C:\Users\Mark\AppData\Local\Temp\
Free temp space: 932,576 MB
Error ID: 5674
Error detail: OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at Libronix.SearchEngine.DocumentIndexer..ctor(Indexer indexer, Int32 nId, LexiconCache lexicon)
   at Libronix.SearchEngine.Indexer.BeginDocument(String strDocumentId)
   at Libronix.DigitalLibrary.Documents.PassageList.PassageListDocument.IndexCore(Indexer indexer, IWorkState state)
   at Libronix.DigitalLibrary.Documents.DocumentManager.DoBuildIndex(IPausableWorkState state, DocumentManagerIndexData data)
   at Libronix.Utility.Threading.WorkStateThreadOwner`1.ThreadProc(Object objData)
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart(Object obj)

Find more posts tagged with

Comments

Bradley Grainger (Logos)

Logos 5 was rebuilding an index of your documents (for the "My Content" section) in the background, when it ran out of memory.

Unfortunately, it's hard to diagnose these errors; the document indexer may have just been the victim of some other tool or panel that used up all the memory. Nevertheless, it was indexing passage lists at the time; do you happen to have any (or several?) large passage list documents (with thousands of verses, or more)? If so, how many passages are in them?

Mark Barnes

https://community.logos.com/discussion/comment/412783#Comment_412783

Unfortunately, it's hard to diagnose these errors; the document indexer may have just been the victim of some other tool or panel that used up all the memory. Nevertheless, it was indexing passage lists at the time; do you happen to have any (or several?) large passage list documents (with thousands of verses, or more)? If so, how many passages are in them?

I have only six passage lists, each with only a few dozen verses in them. Only two had been changed and would need indexing - one had six verses, the other was blank.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/412863#Comment_412863

I have only six passage lists, each with only a few dozen verses in them. Only two had been changed and would need indexing - one had six verses, the other was blank.

Thanks for the update.

As I wrote earlier, there may have been something else using a lot of memory, and the indexer just happened to be the program component that drew the short straw (and pushed the program over the edge).

You may wish to keep an eye on the memory column for Logos.exe in Task Manager and see if there's some operation you perform that spikes it up to 500+ MB. If it's reproducible, we can test it here to find if there's a memory leak or other problem we need to look at.

Mark Barnes

https://community.logos.com/discussion/comment/413172#Comment_413172

I just had another crash (this time with SR-3), with the same error message. I was running a syntax search at the time, and memory peaked at over 1Gb. Logs attached:

37704.Logos.log

<edit>The search still crashes, even when I run it after my documents had indexed - so in this second case the problem is with syntax searching, not the document indexing.</edit>

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/416046#Comment_416046

I was running a syntax search at the time

It is a known issue that it's possible to run a syntax search that exhausts memory. We have implemented some mitigations in the past (such as reducing the number of results that are returned), but this is obviously not helping in this case.

Can you share or describe the search you were running, so we can try to reproduce?