And now, a show stopper, for me anyway...

[ElAurens]

I have six gigs installed.

Last night when this happened I looked in the task manager and just over 5 gigs were being utilized.

There is a massive memory "leak" or whatever it really is, going on.

[335th_GRAthos]

Originally Posted by ElAurens

I have six gigs installed.

Last night when this happened I looked in the task manager and just over 5 gigs were being utilized.

There is a massive memory "leak" or whatever it really is, going on.

That's it then!

Interestingly enough, it seems it happens (the programm eats memory) when in gunsight mode (I need to test more).

For me the solution is easy: I start flyng CoD at 78% RAM utilised (my RAMDISK eats 6Gb RAM). When I see my RAM at 96% used, I close the game and restart it.

The nice thing is that the online servers keep my kill ration when I get connected again


But please, do not tell me that you start a new gameand a single explosion can eat up all your memory!!!!????


~S~

Originally Posted by 335th_GRAthos

That's it then!

Interestingly enough, it seems it happens (the programm eats memory) when in gunsight mode (I need to test more).

For me the solution is easy: I start flyng CoD at 78% RAM utilised (my RAMDISK eats 6Gb RAM). When I see my RAM at 96% used, I close the game and restart it.

The nice thing is that the online servers keep my kill ration when I get connected again


But please, do not tell me that you start a new gameand a single explosion can eat up all your memory!!!!????


~S~

Grathos...We cant expect that every single CLOD customer is HW and SW expert. And that he will free up his RAM even though he has 6 or 8 GIGS which should be enough for EVERY modern and properly optimised sim, no matter how complex it is. So lets just wait the optimisations.

[Chivas]

Interesting... I know that exposions caused problems with the last beta, but I thought it was fixed in the release candidate.

[satchenko]

Try with something like this, maybe works:
http://www.fcleaner.com/ramrush.htm

[CaptainDoggles]

Originally Posted by ElAurens

I have six gigs installed.

Last night when this happened I looked in the task manager and just over 5 gigs were being utilized.

There is a massive memory "leak" or whatever it really is, going on.

It's called a memory leak.

What happens is the program allocates memory, but doesn't release it later.

So more and more memory keeps being allocated (reserved by CLOD) and as a result the OS has less and less memory to work with, until it can no longer function and the process crashes.

[Insuber]

In my case, it's enough to let CloD alone, even minimized, to see the RAM being slowly eaten up, kb after kb, until freezing and crash to desktop occurs @ around 6.5 GB (out of 8 GB). Certain events, such as zooming the view on a plane or object, or watching an explosion, seem to fill the RAM more quickly.

Cheers!

[albx]

Originally Posted by CaptainDoggles

It's called a memory leak.

What happens is the program allocates memory, but doesn't release it later.

So more and more memory keeps being allocated (reserved by CLOD) and as a result the OS has less and less memory to work with, until it can no longer function and the process crashes.

Some time ago I made a thread about memory leak, everybody jumped over me telling I was wrong, blablabla and the mods deleted the thread. Seems I wasn't so wrong then or not dear mods?

[tintifaxl]

Originally Posted by CaptainDoggles

It's called a memory leak.

What happens is the program allocates memory, but doesn't release it later.

So more and more memory keeps being allocated (reserved by CLOD) and as a result the OS has less and less memory to work with, until it can no longer function and the process crashes.

No that's not what happens in this case. CloD crashes, when it reaches the 4Gig barrier for 32bit apps. It asks for more ram -> the the operating system denies it -> crash.

Doesn't matter if you have 6, 8, 16 or 32 Gigs of ram installed. CloD can use only 4 Gig of it.

[Feathered_IV]

Originally Posted by tintifaxl

No that's not what happens in this case. CloD crashes, when it reaches the 4Gig barrier for 32bit apps. It asks for more ram -> the the operating system denies it -> crash.

Doesn't matter if you have 6, 8, 16 or 32 Gigs of ram installed. CloD can use only 4 Gig of it.

Interesting, thanks!

As I understand it, clod doesn't use 64 bit effectively (or at all) as yet, but could one expect the memory limitation to improve if 64' ever does get implemented?