Crash: 4.0c: Out Of Memory Exception, searching for Highlighted text with wildcard (*)

MAJOR EDIT/REVISION: (Don't know if this is relevant: Logos was still indexing after I'd downloaded and started 4.0c and been indexing for a while.) I opened a Search panel, clicked the "All text" dropdown, clicked the main Highlighter Pens checkbox, which caused all three of the highlighter pen colors available -- "Pink highligher; Red Highlighter; Yellow Highlighter" (which I'm guessing must be all of the highlighting colors I've ever used) -- to be selected. I wanted to search for any highlighted text, yet it wouldn't let me start the search without something in the Find box, so on a whim I tried the wildcard character *. Logos churned on this for a while and then crashed. The crash was an Out of Memory Exception.

Here are my Log Files: 7658.Logos_4.0c_Crash_OutOfMemory_Exception.zip

And here's what Task Manager was reporting about my memory usage (after Logos terminated; unfortunately I neglected to check while Logos was still crashed but in memory):

Perhaps I really was out of memory while Logos was running, but I find that hard to believe. I have 8GB of RAM and gobs of free hard disk space. I did have a few other apps running at the time (IE, Outlook, Word), but nowhere near how I sometimes tax my system. According to Task Manager, I was only using 44% of my physical memory (after Logos had shut down). Could Logos have been using up all the rest and then running out when trying to allocate more? I suppose so.

Anyway, Logos should put up an error message and allow the user to close it down gracefully if it is unable to allocate needed memory, rather than crashing.

Find more posts tagged with

Comments

Melissa Snyder

Indexing generally affects CPU usage more than memory. I can report this crash along with your suggestion for an error message rather than a crash.

Edit: I tested a search for * wildcard with one highlighter selected, searching a small collection of Bibles, and it was using 60-70% of the physical memory in my virtual test machine during this process. It's still thinking about it, hasn't crashed (yet).

Rosie Perera

https://community.logos.com/discussion/comment/109797#Comment_109797

If it was still indexing, that generally affects CPU usage more than memory. I can report this crash along with your suggestion for an error message rather than a crash.

Yes, please! There is never any excuse for crashing when you've still got enough memory left to put up an error message. And if Logos could allocate some emergency memory up front, then if it ever does reach a situation where memory is so depleted that it cannot continue at all, it at least has enough memory to put up such an error message. Winding down to exit the program prematurely could also probably be completed gracefully this way. There's not much memory needed in closing down, because you're generally releasing memory at that time.

Newbie users should never have to face that dreaded "Not responding" or Windows app crash message box. Most of them haven't the slightest clue what to do, and it only erodes people's confidence in the robustness of Logos, which doesn't need any more eroding at this time.

Melissa Snyder

https://community.logos.com/discussion/comment/109808#Comment_109808

Searching for "*" will no longer crash the application, in normal use, in 4.0c Beta 2. If an OutOfMemoryException occurs after Beta 2 is released and installed (most likely due to memory usage being already high), we will revisit this.