Indexer has 100% CPU usage on Windows 7 and then crashes.

Hi, I just installed Logos 4.3 and was trying to merge old resources from the older Libronix version. However, when the Indexer tries to build or even rebuild from scratch, when it gets to around 4% progress, CPU usage goes to 100%, then I get notices from Norton and without any other notice, the indexer crashes, sometimes giving me the warning that Logos 4 "stopped working." Do I need to keep the main Logos 4 window open? I've tried it both ways.

What do I do to get indexer to continue past 4% without crashing? Thanks for any help you can offer.

Tom

Find more posts tagged with

Comments

Dave Hooton

Disable Norton or tell it not to sweep the \Logos4 path (C:\Users\username\AppData\Local\Logos4). If it still crashes we need to see some logs to diagnose the crash, but please explain how you are 'merging' resources and exactly what CPU is on your computer (+ memory, etc).

Thomas Luttrell

https://community.logos.com/discussion/comment/276837#Comment_276837

Norton isn't "sweeping" in that it isn't the virus scanner that I'm talking about. It just gives the warning that Logos 4 Indexer is using 100% CPU. I have an AMD A-8 and 6 GB of RAM, with Windows 7 running.

Also, I read somewhere that logging was disabled in L4.3, is that correct? How do I go about doing that?

I didn't see my old Libronix resources, so I installed Libronix on this computer and all of my old resources. Then I closed that and opened Logos 4 to have it auto-detect the new resources. Therefore, I'm sure it's trying to index a ton of old resources (around 800 under Libronix), and that it will take a long time to do that. I just don't want it to crash or hang everytime it gets to 4%. This time, it hasn't crashed yet, but it's been at 4% for awhile now. I have no way of knowing if it's just frozen.

Thomas Luttrell

https://community.logos.com/discussion/comment/276840#Comment_276840

This is my index crash log:

Program Version: 4.3 (4.30.0.1516)
Windows Version: 6.1.7601.65536
Time: 2011-08-15 17:02:44
Installed memory: 5,610 MB
Install path: C:\Users\Tom\AppData\Local\Logos4\System\Logos4Indexer.exe
Data path: C:\Users\Tom\AppData\Local\Logos4\Data\j03vodp2.zio
Free disk space: 509,316 MB
Temp path: C:\Users\Tom\AppData\Local\Temp\
Free temp space: 509,316 MB

Error ID: 2822
Error detail: IndexingException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Libronix.DigitalLibrary.Logos.IndexingException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Data.SQLite.UnsafeNativeMethods.sqlite3_step(IntPtr stmt)
   at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
   at System.Data.SQLite.SQLiteDataReader.NextResult()
   at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
   at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.SQLite.SQLiteCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()
   at Libronix.Utility.Data.PoolableConnector.ExecuteReader(String strText, Object[] aobjParameterNamesAndValues)
   at Libronix.DigitalLibrary.Resources.ReverseInterlinear.ReverseInterlinearResourceCore.GetTranslationWordsForMappings(IWorkState state, IConnector conn, IList`1 listMappingIds, VerseReference verse)
   at Libronix.DigitalLibrary.Resources.ReverseInterlinear.ReverseInterlinearResourceCore.AlignTextForMappings(IWorkState state, IConnector conn, Int32 nMinDocumentPosition, Int32 nMaxDocumentPosition, Nullable`1 nMappingId, Nullable`1 nSelectedWordDocumentPosition)
   at Libronix.DigitalLibrary.Resources.ReverseInterlinear.ReverseInterlinearResourceCore.GetTextAlignment(IWorkState state, Int32 nStartDocumentPosition, Int32 nEndDocumentPosition)
   at Libronix.DigitalLibrary.Resources.ReverseInterlinear.ReverseInterlinearResource.GetTextAlignment(IWorkState state, Int32 nStartDocumentPosition, Int32 nEndDocumentPosition)
   at Libronix.DigitalLibrary.Logos.LogosResourceIndexer.ProcessReverseInterlinearIndexData(NativeLogosResourceIndexer* pNativeIndexer, Char* pszSourceId, ReverseInterlinearColumnIndexData* pData, Int32 nDataCount)
   at Libronix.DigitalLibrary.Logos.LogosResourceIndexer.DoProcessReverseInterlinearIndexData(NativeLogosResourceIndexer* pNativeIndexer, Char* pszSourceId, ReverseInterlinearColumnIndexData* pData, Int32 nDataCount)
   at Libronix.DigitalLibrary.Logos.Callback.ProcessReverseInterlinearIndexData(Callback* , NativeLogosResourceIndexer* pNativeIndexer, Char* pszSourceId, ReverseInterlinearColumnIndexData* pData, Int32 nDataCount)

   --- End of inner exception stack trace ---
   at Libronix.DigitalLibrary.Logos.Callback.{dtor}(Callback* )
   at Libronix.DigitalLibrary.Logos.LogosResourceIndexer.DoIndexResource(IDocumentIndexer documentIndexer, IWorkState workState, TitleLoader* pTitleLoader, basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >* strReverseInterlinearDataType, Boolean bCurrentTitleSupportsMorph)
   at Libronix.DigitalLibrary.Logos.LogosResourceIndexer.IndexResource(auto_handle<Libronix::SearchEngine::IDocumentIndexer> documentIndexer, IWorkState workState, TitleLoader* pTitleLoader, Boolean bCurrentTitleSupportsMorph)
   at Libronix.DigitalLibrary.Logos.LogosResource.IndexContent(IIndexer indexer, ResourceManager resourceManager, ReverseInterlinearManager reverseInterlinearManager, LibraryCatalog libraryCatalog, IWorkState state)
   at Libronix.DigitalLibrary.LibraryIndex.IndexNextResource(ILibraryIndexWorkState state, Indexer indexer)
   at Libronix.DigitalLibrary.LibraryIndex.SecondaryIndexThread(Object objState)
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart(Object obj)

Thomas Luttrell

https://community.logos.com/discussion/comment/276846#Comment_276846

I'm about to give up and ask for a refund on Logos 4!

Dave Hooton

https://community.logos.com/discussion/comment/276840#Comment_276840

I have an AMD A-8 and 6 GB of RAM, with Windows 7 running.

Sounds like the problem in this thread (click on the blue words which are a hyperlink). The workaround appears further down.

I read somewhere that logging was disabled in L4.3, is that correct?

That is incorrect. Click on the blue hyperlink in my previous post to see the wiki article on logging.

Thomas Luttrell

https://community.logos.com/discussion/comment/276849#Comment_276849

I tried a clean install again of Logos 4, and it got through downloading everything, but once it started indexing, it crashed again. I got a similar error:

Thanks for referring me to that link. Yes, I do have an HP with an AMD A-8 processor, and apparently others are having a similar problem on these computers. Thanks for pointing this out. I just hope that by changing the affinity of the process to one CPU that it solves the problem. We'll see.

Thomas Luttrell

https://community.logos.com/discussion/comment/276874#Comment_276874

Dave, thanks for pointing me in the right direction! Your help is greatly appreciated!

By switching the process to one CPU only, the indexer is making more progress now than it ever has before. I think this may have been a good solution. Let's just hope I don't hit anymore snags, but if you don't hear from me again, you can assume that it's working. Thanks! [:)]

Update: My Logos 4 is now completely indexed and the installation is finished. Thank you for the help. Limiting the process to one CPU took care of the problem. Hopefully this bug will be fixed so that future users will not have to waste a lot of time like I did. It appears that the index software has trouble with this AMD quad processor.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/276884#Comment_276884

Limiting the process to one CPU took care of the problem. Hopefully this bug will be fixed so that future users will not have to waste a lot of time like I did. It appears that the index software has trouble with this AMD quad processor.

Hi Thomas,

I spent today working on this crash, and I think I found a fix (which will be in 4.3 SR-1).

We still don't know exactly why the indexer crashes with tihs particular quad-core processor (although it works fine on Intel CPUs), but the fix we developed today should let the indexer complete successfully (while still using all four cores, for speed).

I apologise for the inconvenience and thank you for your patience in waiting for SR-1.