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

H2SO4 said:

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

H2SO4 said:

(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

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

ok thanks
will let you know when it happens

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

here is a pic of task manager

cheers brad