Crash: 4.0c Beta 2: OutOfMemoryException thrown, Logos was just sitting idle
I've been seeing OutOfMemoryExceptions more frequently lately. I have 8 GB of RAM so it shouldn't be happening, though I do take my computer through its paces and often have lots of apps running simultaneously along with Logos.
I had recently downloaded some of the new Zondervan titles and allowed Logos to complete indexing. I had several resources open in Logos from the last time I'd shut it down, but primarily one which I was looking things up in: the Oxford Dictionary of the Christian Church. I was copying links of the format "libronixdls:jump|pos=LLS-AOL:0<ISAAC.OF.NINEVEH>.0.0|res=LLS:ODCC" and pasting them into the command bar and hitting Enter. I did that maybe eight times. After the last time, and then a pause while I went off to the web to do some other stuff, Logos decided to crash on its own while I wasn't even interacting with it.
Log files attached: 2577.Crash_2010-04-05.zip
Comments
-
My guess is that you have an open search panel (or a visual filter document) that's searching the entire library for "*". Not only will this be dragging down the performance of the application (because it's running multiple searches in the background), Logos 4 does not currently coordinate the efforts of this background work well enough to avoid an OutOfMemoryException.
I recommend closing any open search panels and deleting any visual filters that have "*" as the query.
(Also, it's not necessary to run Debug logging; not only will it slow down Logos 4 to log that extra data, it makes it very difficult to find the useful information amid all the debug output when reading your log files.)
0 -
Bradley Grainger said:
(Also, it's not necessary to run Debug logging; not only will it slow down Logos 4 to log that extra data, it makes it very difficult to find the useful information amid all the debug output when reading your log files.)
How do you turn off Debug logging once it's been enabled? I can't even remember how I enabled it (something to do with Logos4.exe.config?) and I don't seem to have kept a backup of that file from before it was enabled.
0 -
Logos Platinum
Windows 7 - 64 Bit
Lenovo laptop E520 i7-2640M, 2.8GHz 8G Ram, 2G GraphicsAustralia
0 -
David Gullick said:
I know about that, but that's how to turn off basic diagnostic logging. There's a second more verbose level of logging called debug logging that Bradley was talking about. It's what makes reading the logs a chore because there's too much information in there. It isn't widely publicized because they don't want everyone using it. They'll only ask you to enable it to get more details if they're having a hard time tracking down a particular bug. I can't remember how/where I found out about it and enabled it.
I choose to leave basic logging on all the time because if Logos suddenly crashes unexpectedly, I want to be able to provide logs in case I can't reproduce the crash. I'm willing to take the speed hit for that. If I turned off this kind of logging I wouldn't have any log files generated at all. Just the crash text report, which is often not sufficient to track down what caused the crash.
0 -
Rosie Perera said:
How do you turn off Debug logging once it's been enabled? I can't even remember how I enabled it (something to do with Logos4.exe.config?) and I don't seem to have kept a backup of that file from before it was enabled.
Delete the Documents\Logos Log Files\Logos4.NLog.config file.
0
