Memory Leak, Still??

So, I run a process explorer program similar to task manager so that I can set WoWP.exe to run at high priority. It also shows me readouts of mem and cpu usage. The other day, I caught WoWP.exe using up 2.7gig of RAM. It seems to use closer to 1gig when it's started up. Is this still the memory leak? I have 12 gig so I don't think I've ever had the mem leak crash, but it seems an awful lot of memory usage when the min requirements are 3 gig and we've had so much optimizations in recent patches (hangar loading aside!).

I have yet to hit the memory leak crash myself within the past month, but I've found it crashes if you hit the 32-bit (32 bit program) memory address limit.. which is roughly 4GB on the mark or if you exceed the amount of free memory you have.. as soon as it goes over that the game just locks.

In my case, it only happens if I play for around 7 hours continuously. That is rare for me. xD

"The thing about perfection is that it's unknowable. It's impossible, but it's also right in front of us all the time."
- Kevin Flynn

You would think fixing this would be on their "must have" list for the game's release.

I am sure it high on the list ,but it not like making one fix for just one PC ,and one system
renumber any fix on any thing addressed must work one as many PC to systems as as out there,and then add the addition problem of added equipment after you PC is out of the box. Like adding Vid ,and sound cards.

I am sure it high on the list ,but it not like making one fix for just one PC ,and one system
renumber any fix on any thing addressed must work one as many PC to systems as as out there,and then add the addition problem of added equipment after you PC is out of the box. Like adding Vid ,and sound cards.

Actually, a memory leak proble IS a "one size fits all" fix. You plug the memory leak and ALL systems will perform better. It's a very generic system level problem, unlike a video card driver mis-match or a hardware conflict.

It is like improving a road surface and fixing pot holes and such. It doesnt matter what kind of car drives on it...it still see's the improvement.

I had a HUGE problem with this when I was running a 32 bit windows system. It has completely disappeared since switching to a 64 bit system, getting a 4 gig video card and upping my system memory to 8 gigs.

A memory leak is like a virtual oil leak in your computer. It slowly drains the available memory, reducing the amount of free memory the system can use. Most memory leaks are caused by a program that unintentionally uses up increasing amounts of memory while it is running. This is typically a gradual process that gets worse as the program remains open. If the leak is bad enough, it can cause the program to crash or even make the whole computer freeze.
The most common reason programs have memory leaks is due to a programming error where unused memory is not allocated back to the system. This means the amount of RAM the program uses is always growing. Therefore, the program is constantly "leaking" memory. A memory leak may also be caused by a program that requests new memory too frequently, instead of using available memory. This means each time more memory is requested, the program takes up additional RAM instead of using memory that has already been made available to the program.
Fortunately, memory leaks are not as messy as oil leaks and can be more easily fixed. Software development applications often include debuggers that can check programs for memory leaks. Once the source of the leak is found, the programmer can modify the code so that the program uses memory more efficiently. If you are using a program that has a memory leak, you can temporarily fix the problem by simply quitting the program and opening it again. Once the program has been quit, the memory is automatically allocated back to the system. Of course, if the leak continues to be a problem, the best solution is to let the developer know about the issue so it can be fixed.