L4 consistently chews through memory until it crashes

Hello everyone,

For quite some time now I've had the frustrating problem of L4 crashing frequently. I thought it might just be a corrupt installation, so this week I did a totally clean install from the internet onto my laptop (P4 1.8GHz, 1 GB). I then used method 3 (from the wiki) for installing on multiple computers to put it on my desktop (P4 3.2GHz, 2 GB, 128mb DX9 graphics) since I don't have internet at home (I can occasionally borrow a wireless broadband card but can't do massive downloads). It did not solve the issue, so I did some more detailed checking. If I enter a passage on the home screen and hit Go (I was using Jn 4:1-38) it starts bringing things up and filling in the guides. The memory use (viewed in the Task Manager) goes up and up until it crashes. On the desktop with 2GB ram this happens when L4 gets up to about 1100-1300 mb of memory use. Then I get the windows error reporting trying to report a system.outofmemoryexception error. On the laptop it happens around 850 mb of use (out of 1GB). My version number is 4.01.3.4767 (4.0a SR-2). I did search the forums for memory related crashes but found mostly stuff related to 4.0a SR-2 indexing which I'm not doing (at least, the indexer isn't running, and I think it was done).

I've tried doing just a passage guide or just an exegetical guide (not the full Go button layout) but it still happens. I've tried creating my own custom PG and EG with fewer sections but no luck. I think it also happens when I have just a couple of bibles plus BDAG open. It seems like there's a memory leak or something. I've attached a log file from one time when it crashed on the desktop.

Anyway, it's pretty much unusable for any serious study. My machines meet the minimum requirements, so this is frustrating. I know I really should get more ram, etc, etc. But I have what I have, and I feel like crashing when it runs out of memory shouldn't be normal behaviour. I would be very grateful for any help anyone could provide. Many thanks in advance!

Peace in Christ,

Steve

Log: 8688.Logos4.log

Find more posts tagged with

Comments

Jeremy

Mine has a related problem. It chews through money until my checkbook crashes. Is there a fix for this?

Steve M.

https://community.logos.com/discussion/comment/72850#Comment_72850

Haha! I think the logos forums may not be the best place to find that kind of help.

Oh, I forgot to say that both machines are Win XP SP3.

Jeremy

https://community.logos.com/discussion/comment/72853#Comment_72853

Are you only running Logos4? I too am running XP with 1 gig of RAM and although it is slow, it doesn't crash. It starts up a heck of a lot slower than L3, but the Greek and Hebrew word studies are so much faster. Maybe turn off your wifi or internet and your antivirus. One more thing, how much memory is being used when you aren't using L4?

Todd Phillips

Log: 8688.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/8688.Logos4.log]

That log only has 5 minutes of data...is that how long it takes before it crashes? It also doesn't have any errors in it.

Did you restart Logos after the crash, but before uploading the log? Logos restarts the log file whenever it is restarted, so you need to make sure you upload the log file before restarting Logos. (Also, some users have had to wait 5 or 10 minutes after a crash to have severe errors finish writing to the logs--not me personally)

Mark Smith

Steve,

The log file doesn't actually show a Logos crash. This is consistent with what you are reporting. Windows seems to be crashing or closing the program.

You might begin by being sure you have enough virtual memory allocated. You didn't say what your operating system is. In W7 the default is to allow Windows to manage virtual memory which normally precludes problems. If you have set a virtual memory size below 2 GB (2048 MB) you might try increasing it.

There might be some other issues, including a problem on the RAM chip itself, but I think that is not what is causing the trouble.

Keith Larson

Steve,

For what it is worth this is not normal behavior for Logos. I have ran it on several different systems XP, Vista 32, Win7 32 and 64 and under all these operating systems I have be surprised by how little memory it uses. Beyond this confirmation that this is not normal behavior, I cannot offer you any assistance. This sounds like a problem for customer support.

Steve M.

https://community.logos.com/discussion/comment/72867#Comment_72867

I thought it only writes a log when you start up holding Ctrl. I had opened L4 since, but not using Ctrl. Previous times when I have looked through the logs right after a crash I have also not seen errors recorded. But in any case, I haven't exited L4 normally in a long time. It always crashes. And if it crashes, perhaps it doesn't have time to write the error into the log.

Anyway, I'll be away from my computer for a while, but later I will try to do it again and post another log. Thanks for your response!

Steve M.

https://community.logos.com/discussion/comment/72876#Comment_72876

That last response was to Todd. Sorry, there were two more posts while I was typing my reply.

Mark, it's Win XP SP3 on both machines. I will try increasing the virtual memory (it was starting at ~750mb with a max of ~1500). I doubt it's a hardware issue because it happens on both machines. Thanks for the suggestions!

Keith - Yeah, I may need to try customer support. We'll see if any on the forums has any ideas that may help me for the weekend.

Steve M.

https://community.logos.com/discussion/comment/72887#Comment_72887

It just crashed again on the desktop, and I'm posting the log. This time it has some more interesting stuff at the bottom: 34562.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/34562.Logos4.log]

Thanks.

Mark Smith

https://community.logos.com/discussion/comment/72887#Comment_72887

I will try increasing the virtual memory (it was starting at ~750mb with a max of ~1500).

The laptop might have trouble with those limits. I consistently am using about 2.5 - 3 GB of memory when Logos is actually doing some work.

Steve M.

https://community.logos.com/discussion/comment/72890#Comment_72890

Not sure if that upload worked. I'll try again.

By the way, this is without anything else running (no internet, no browser, antivirus disabled, everything else closed).

3223.Logos4.log

Mark Smith

https://community.logos.com/discussion/comment/72894#Comment_72894

Steve,

The last lines in that Log refer to something Logos was doing with a specific resource: the Louw-Nida Semantic Domains lexicon. Is that resource open when you open up Logos 4?

I'm assuming you are not opening to a blank layout. What resources and tools are open when you open L4?

As a minimum, if you have Louw-Nida open, close it. Remember that a word study might be trying to access it, or 'Cited By' if that is open (at least two I can think of, there are probably more.) You should close those if they are open.

Steve M.

https://community.logos.com/discussion/comment/72982#Comment_72982

Mark, et al.,

I increased the virtual memory on both machines. For example, on the desktop which has 2GB ram I bumped the VM up to start at 2GB and max out at 4GB. But the problem persists.

I open to the home screen with no resources open (except those the homepage points to) and then type a passage in the Go box. I know that the exegetical guide accesses Louw-Nida, so I took Louw-Nida out of my prioritized resources so it would not try to access it any more. This also did not solve the problem.

Here is an updated log after both of these trouble-shooting steps were taken. At the bottom there's record of an unhandled exception being thrown, which is apparently the cause of the crash: Error OurApp Unhandled exception: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

Log: 2570.Logos4 incr VM no LN.log

Thanks for all the help everyone! I'm beginning to think I'll have to try to contact support directly.

Mark Smith

https://community.logos.com/discussion/comment/73283#Comment_73283

I'm beginning to think I'll have to try to contact support directly.

Yep. I think that's what you'll need to do. Let us know how you get things fixed once you do.