4.6 Beta 5 (4.60.0.2948) Windows Crash While Tagging in Library

1. Was in MyLibrary

2. Was "re-tagging" - originally I had about 4 "mytags" on this particular resource [the original tag had been "toberead" - I changed it to "read"

3. "Message: "Logos has stopped working..."etc

After looking at logs: QUESTION: HOW COULD IT POSSIBLY THROW AN "OUT OF MEMORY"? Obviously that phrase means something very different when this computer features 12 Gigs of Ram and at least half of its 500 Gig hard drive being empty.

Program Version: 4.6 Beta 5 (4.60.0.2948)

Windows Version: 6.1.7601.65536

Time: 2012-08-26 22:40:42 -04:00 (2012-08-27T02:40:42Z)

Installed memory: 12,217 MB

Install path: C:\Users\8740-\AppData\Local\Logos4\System\Logos4.exe

Free install space: 264,192 MB

Data path: C:\Users\xxxx\AppData\Local\Logos4\Data\pndpol3m.kun

Free disk space: 264,192 MB

Temp path: C:\Users\xxxx\AppData\Local\Temp\

Free temp space: 264,192 MB

Error ID: 707

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.LibraryCatalogIndex.DoBuildIndex(IPausableWorkState state)

at Libronix.DigitalLibrary.LibraryCatalogIndex.BuildIndexThread(IPausableWorkState state, LibraryCatalogIndexData data)

at Libronix.Utility.Threading.WorkStateThreadOwner`1.ThreadProc(Object objData)

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)

Find more posts tagged with

Comments

SteveF

Not re-producable.

Bradley Grainger (Logos)

QUESTION: HOW COULD IT POSSIBLY THROW AN "OUT OF MEMORY"? Obviously that phrase means something very different when this computer features 12 Gigs of Ram

Warning: This discussion is about to get quite technical. (For the super-technical nerds amongst us, note that I will simplify the discussion a little and will be ignoring AWE, /LARGEADDRESSAWARE, etc.)

Logos 4 is a 32-bit application. This means it can access at most 2³² bytes of memory = 4GB. (This is known as the "virtual address space".) The Windows kernel reserves 2GB of this space for itself, leaving 2GB available for the application. .NET and other libraries use up about another 1GB, leaving 1GB available for Logos 4 to use to store data while it's running.

A simplified way of undertstanding this is that if Logos 4 uses more than (roughly) 1GB RAM while it's running, it will throw an OutOfMemoryException, no matter how much physical RAM you have installed. (Thanks to "virtual memory" in modern OSes, this could happen if you have 1GB or 32GB of physical RAM.)

A solution to this problem is for us to rewrite Logos 4 to be a 64-bit application. Some factors complicating this are:

Some of the Logos code is very old, and might break if recompiled as 64-bit.
Not all of our users are running 64-bit operating systems. To keep supporting them, we would need to ship 32-bit and 64-bit versions of Logos in parallel; this makes the installer more complicated. (This becomes less of a problem each year as more 64-bit OSes are deployed.)
64-bit code requires more memory by default (because each "pointer" in the application doubles in size). If the 32-bit application requires 2GB RAM as a minimum, the 64-bit application might require 3GB. (This becomes less of a problem each year as new computers ship with more RAM by default.)
64-bit code might hide memory leaks. Because of the 16TB virtual address space that 64-bit processes get, memory leaks could go unnoticed for a long time, but would slow down the application (because each .NET garbage collection would take longer).

I previously touched on this here: http://community.logos.com/forums/p/22045/167346.aspx#167346. Two years have elapsed, so not everything in that post reflects our latest thinking.

SteveF

https://community.logos.com/discussion/comment/391671#Comment_391671

Thanks so much, Bradley.

This does help. [:)] [I think [:)]]