Windows 7 Memory Leak?

SoLoR said:

x-fi ? :) lots of us have this issue, there is workaround avilable, if you disable "sound blaster enchantments". Other then that, whine to creative...

Yep, and the stupid thing is it doesn't happen every time I play either.

usasma said:

The only documented memory leak that I've seen is when running CHKDSK /R on another volume (other than C:). It'll quickly suck up all the memory that you have.

That is not a memory leak, that is by design. It will not hold on to that memory either.

logicearth said:

That is not a memory leak, that is by design. It will not hold on to that memory either.

Eloborate why is it by design

EarlZ said:

Eloborate why is it by design

Engineering Windows 7 : What we do with a bug report?

...the memory usage was by design and was a specific Windows 7 change for this scenario (the /r flag grabs an exclusive lock and repairs a disk and so our assumption is you’d really like the disk to be fixed before you do more stuff on the machine...

Thanks for your replies. I too have an X-fi sound card but also seem to have discovered a new problem , now with my Antivirus (NOD32 ESET).Computer is extremely slow after startup until i disable it.

I had same problem ( 4 gigs ) booting the system used mem. was .992 to 1.25 gigs . Just exploring folders on HD`s used mem. built up to 2.4 gigs and even more w. out running any program . Some 1 to 1.5 gigs of mem. could not be identified not in Task Manager nor in Resource Monitor or in Procexe .

I am almost sure the problem was SOLVED after DEFRAG the System disk ( c: ) with Defragler from Piriform . !!! There were some 12% of fragmented files with more then 15,000 fragments , I suspect the fragments inflated the Kernel Memory .

Would Someone check that solution to be sure that`s the problem .

Now My System is working nice for the last few days the Used Memory is going up and back down as running or closing Programs .

mmarcu said:

I had same problem ( 4 gigs ) booting the system used mem. was .992 to 1.25 gigs . Just exploring folders on HD`s used mem. built up to 2.4 gigs and even more w. out running any program . Some 1 to 1.5 gigs of mem. could not be identified not in Task Manager nor in Resource Monitor or in Procexe .

I am almost sure the problem was SOLVED after DEFRAG the System disk ( c: ) with Defragler from Piriform . !!! There were some 12% of fragmented files with more then 15,000 fragments , I suspect the fragments inflated the Kernel Memory .

Would Someone check that solution to be sure that`s the problem .

Now My System is working nice for the last few days the Used Memory is going up and back down as running or closing Programs .

While I'm very glad that your issue is seemingly resolved, I'd like to assure you that no amount of fragmentation will by itself cause a "memory leak". The way that individual files and their fragments are stored on disk does not directly map to their in-memory layout. Also, a "leak" is a very specific type of software defect - a bug in other words - which can only be resolved by a code-level reworking.

There are literally squillions of different possible leak causes. Just because somebody else thinks they have a "memory leak" doesn't mean it's the same issue.

While I'm very glad that your issue is seemingly resolved, I'd like to assure you that no amount of fragmentation will by itself cause a "memory leak". The way that individual files and their fragments are stored on disk does not directly map to their in-memory layout. Also, a "leak" is a very specific type of software defect - a bug in other words - which can only be resolved by a code-level reworking.

There are literally squillions of different possible leak causes. Just because somebody else thinks they have a "memory leak" doesn't mean it's the same issue.

Hi H2SO4 , thanks for Your attention and be careful with the ACID !!!

I am in computers from the 70th`s fairly I can say I am an expert on Hardware , Software I manage well but isn`t "My strong side" .

I`ve installed the W7 x64 on a brand new machine Gigabyte P45-UD3 , E8400 , 4g. Kingston ( 2x2) , Gigabyte ATI 4850 ( 1g.) , Wd. Green 320 g. , Wd Green 1 t. , two others 160g. HD`s .

At the begining all worked fine the used mem. was .9 to 1.25 g. after boot going up to 2 - 2.6 g. and down with opened and closed programs usually going back to 1.25 - 1.35 g.

Working with hundreds of .rar on the C: I`ve noticed the used mem. build up to 2.5 g. and stay there for hours without going down then I`ve seen that just exploring folders used mem goes up over 2 g.

1 to 1.5 g. of memory could not be identified as used by programws or services not in Task Mngr. or Procexe nor on Resource Monitor .

After the defrag on C: , about 7 days ago the machine went back to normal operation there should be a good reason for sure isn`t a Hardware problem .