Memory leak crash in Incarnate trials

I've been crashing during Incarnate trials recently, particularly Lambda sector. Most times CoH freezes and it takes a Ctrl-Alt-Del to raise Task Manager and kill the exe.

However, last time I actually got an error message: client out of memory, and something about the .pigg files.

Didn't copy it to the clipboard, sadly. Will do next time though.

As it's been happening regularly, it appears there might be a memory leak in the Incarnate trials. It's not the first run where it crashes. Usually the second or third, often while zoning, such as from the hospital in Lambda - I'll start keeping count to see if there's a pattern.

My specs: AMD Phenom II X4 955 3.2GHz, 4GB RAM, 10GB pagefile, GeForce 8800 GT with 512MB RAM, Windows 7.

I'm going to reduce the graphics detail to lower the load on the graphics card and see if that makes a difference. Any updates or .log files and I'll post them here.

It's not *just* the incarnate trials that do this, they just happen to be extremely heavy memory (ab)users and so the memory leak is "more pronounced" with incarnate trials. Other things which can produce the memory leak involve simply playing for several hours (and thus loading lots of zone maps over time) or simply using the Base Editor. I can induce a memory leak crash in the Base Editor reliably just by clicking on the Choose Styles button and then sequentially clicking on the room location tabs one after another, forcing a load of each style into memory (which then never gets cleaned up, purged or garbage collected). The Choose Styles memory leak in the Base Editor is so bad that it simply isn't possible for me to click on each room location (low floors, mid floors, high floors, etc.) all the way through without inducing a memory leak crash of the client. The Base Editor is a VERY RELIABLE memory leaker.

And worst of all, this memory leak problem is OS agnostic (it happens to Windows and Mac computers) as well as being Graphics Card agnostic (it happens to NVidia and AMD cards) ... although the AMD graphics cards do seem to be more susceptible to the problem. This leads me to believe that the fault lies within the CoH programming code itself (and if it isn't, I have a hard time understanding why it wouldn't be).

It's the end. But the moment has been prepared for ...

This seems to be a pretty wide spread problem. Make sure you have your drivers up to date. You can use /unloadgfx to clear the memory. I try to do that about every 30 minutes when I am on large teams. It has always worked for me if I remember to do it.