Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: memory leak


01 Nov 2009   #1

win 7 64 RTM
 
 
memory leak

hi all
i am having all memory used up at intermittent times
sometimes 2 hours sometimes it takes 2 days and when it happens media portal has frozen and its used about 900 meg of my 3325 of ram

any body like to help me figure out were the memory leak is

cheers brad


My System SpecsSystem Spec
.

01 Nov 2009   #2

Win7x64
 
 

As discussed previously, it sounds like a resource leak, but the real questions are "what's leaking?" and "can it be worked around without (re)coding the component in question?". This is all assuming you're already on the latest version of all the components involved, which tends to have a way of resolving (embarrassing) known resource leaks

The best way to troubleshoot is to start a Perfmon log straight after a reboot, and to keep it running until the "freeze" symptom manifests itself. Given it can take days, the trick is to keep the log file from growing to a monstrous size. That's done by being selective about what's being monitored, and how often perfmon records a "sample".

As a suggestion, create a Perfmon counter log to record all instances of all counters under the following objects:

- MEMORY
- PROCESS
- PROCESSOR
- SYSTEM
- THREAD

Set the sample interval to say 2 minutes, and kick off the log soon after the next scheduled reboot. Stop the perfmon log only once you're confident that the machine is clearly being all weird in the particular way which you wish to analyse.

If you need more info on how to create the perfmon log, just yell. Ditto if you'd like assistance in analysing it. There's nothing particularly personal in there other than the hostname of your server and the names of the processes running on it.
My System SpecsSystem Spec
01 Nov 2009   #3

win 7 64 RTM
 
 

Quote   Quote: Originally Posted by H2SO4 View Post
As discussed previously, it sounds like a resource leak, but the real questions are "what's leaking?" and "can it be worked around without (re)coding the component in question?". This is all assuming you're already on the latest version of all the components involved, which tends to have a way of resolving (embarrassing) known resource leaks

The best way to troubleshoot is to start a Perfmon log straight after a reboot, and to keep it running until the "freeze" symptom manifests itself. Given it can take days, the trick is to keep the log file from growing to a monstrous size. That's done by being selective about what's being monitored, and how often perfmon records a "sample".

As a suggestion, create a Perfmon counter log to record all instances of all counters under the following objects:


- MEMORY
- PROCESS
- PROCESSOR
- SYSTEM
- THREAD

Set the sample interval to say 2 minutes, and kick off the log soon after the next scheduled reboot. Stop the perfmon log only once you're confident that the machine is clearly being all weird in the particular way which you wish to analyse.

If you need more info on how to create the perfmon log, just yell. Ditto if you'd like assistance in analysing it. There's nothing particularly personal in there other than the hostname of your server and the names of the processes running on it.
ok lol
i will need help to start the perfmon counter log

the ram is climbing now so it shouldn't be long before it happens again

cheers brad
My System SpecsSystem Spec
.


01 Nov 2009   #4

Win7x64
 
 

(Self-plagiarisation)

1) Create a counters.txt file somewhere on your machine with the following contents:

Code:
 
\process(*)\*
\processor(*)\*
\memory\*
\Thread(*)\*
\system\*
2) On an elevated (run as admin) CMD prompt (change <path> to location of counters.txt): logman create counter LeakLog -cf c:\<path>\counters.txt -si 2:00

3) On the same CMD prompt: logman start LeakLog

4) Wait for the symptom to occur...

5) On an elevated CMD prompt again: logman stop LeakLog


The resultant Binary LoG (BLG) file should be in the \Perflogs\Admin folder.

Note that it's also possible to battle the Perfmon UI to perform the same operation, but I'd rather slash my wrists. When asked "what do you really detest about post-XP Windows?", I say "the counter selection mechanism in the new Perfmon UI". Still waiting for somebody to ask me though.)
My System SpecsSystem Spec
01 Nov 2009   #5

win 7 64 RTM
 
 

Quote   Quote: Originally Posted by H2SO4 View Post
(Self-plagiarisation)

1) Create a counters.txt file somewhere on your machine with the following contents:

Code:
 
\process(*)\*
\processor(*)\*
\memory\*
\Thread(*)\*
\system\*
2) On an elevated (run as admin) CMD prompt (change <path> to location of counters.txt): logman create counter LeakLog -cf c:\<path>\counters.txt -si 2:00

3) On the same CMD prompt: logman start LeakLog

4) Wait for the symptom to occur...

5) On an elevated CMD prompt again: logman stop LeakLog


The resultant Binary LoG (BLG) file should be in the \Perflogs\Admin folder.

Note that it's also possible to battle the Perfmon UI to perform the same operation, but I'd rather slash my wrists. When asked "what do you really detest about post-XP Windows?", I say "the counter selection mechanism in the new Perfmon UI". Still waiting for somebody to ask me though.)
ok done all completed successfully
My System SpecsSystem Spec
01 Nov 2009   #6

win 7 64 RTM
 
 

i got perfmon open and got as far as user defined data collector set but it wants an xml file

under user defined it now has a leaklog running is that what you started from the dos prompt

its up to 2300 meg of ram

cheers brad
My System SpecsSystem Spec
01 Nov 2009   #7

Win7x64
 
 

Quote   Quote: Originally Posted by chinga69 View Post
i got perfmon open and got as far as user defined data collector set but it wants an xml file

under user defined it now has a leaklog running is that what you started from the dos prompt

its up to 2300 meg of ram

cheers brad
If you already punched in all the command-line stuff then you don't need to do anything in the Perfmon UI, at least until it comes time to analyse the data.

The "LOGMAN" command by itself (without switches) should now show the LeakLog status as running.

Don't worry too much about the amount of RAM. Just wait until that "freeze" symptom reproduces before stopping the log.
My System SpecsSystem Spec
01 Nov 2009   #8

win 7 64 RTM
 
 

ok thanks
will let you know when it happens
My System SpecsSystem Spec
02 Nov 2009   #9

win 7 64 RTM
 
 

ok it has frozen meadia portal over night here is the log i cant see anything in it

cheers brad



i renamed the file to get it to up load you will have to rename it


Attached Files
File Type: zip LeakLog_000004.zip (128.0 KB, 8 views)
My System SpecsSystem Spec
02 Nov 2009   #10

win 7 64 RTM
 
 

here is a pic of task manager

cheers brad


Attached Thumbnails
memory leak-taskman.jpg  
My System SpecsSystem Spec
Reply

 memory leak




Thread Tools



Similar help and support threads for2: memory leak
Thread Forum
chkdsk high memory usage / memory leak Performance & Maintenance
General Win7 memory leak and Unknown memory usage? Performance & Maintenance
Troubleshooting Excessive Memory Use (Memory Leak?) after playing vid. Performance & Maintenance
Memory Leak Performance & Maintenance
[Help]Memory Leak. All memory drained and used BSOD Help and Support
Win 7 memory leak? Performance & Maintenance
Memory Leak Performance & Maintenance

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:47 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33