lanman777
asked on
Memory Leak in dllhost.exe or files managed by dllhost.exe
We have a server running several instances of dllhost.exe.
We are certain the dllhost.exe file or one of the files it is managing has a memory leak.
How do we identify the specific file, or whether it is the dllhost.exe file itself.
This just started a couple of months ago. Before that we had no problems.
We are certain the dllhost.exe file or one of the files it is managing has a memory leak.
How do we identify the specific file, or whether it is the dllhost.exe file itself.
This just started a couple of months ago. Before that we had no problems.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
yes, with handle.exe
and this is the GUI version:
http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx
and this is the GUI version:
http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx
ASKER
It seems like finding a process, tool, command to chase down a memory leak is a very grey area. You would think these would be more clearly defined.
Seems to be like looking for a needle in a haystack.
Seems to be like looking for a needle in a haystack.
if you have some instances of dllhost but only one "eat" your memory
it probably the dll it running and not the dllhost app.
the tools will help you to find what files running under the dllhost ...
and the is a start...
it probably the dll it running and not the dllhost app.
the tools will help you to find what files running under the dllhost ...
and the is a start...
ASKER
Looks like very good options.
Just for clarification.
If I run this command;
listdlls dllhost.exe
It will show me all of the files dllhost.exe has open, correct?
Just for clarification.
If I run this command;
listdlls dllhost.exe
It will show me all of the files dllhost.exe has open, correct?
that's the idea...
but to make sure that you check the one you want, run it with process id (PID) number instead of name.
in the task manager ,add the PID column from the "view" menu so you will be abable to
see the PID of the process you want to check.
but to make sure that you check the one you want, run it with process id (PID) number instead of name.
in the task manager ,add the PID column from the "view" menu so you will be abable to
see the PID of the process you want to check.
ASKER
I can see how I can identify which dllhost instance has the memory leak by watching the memory on dllhost when I run PSLIST DLLHOST -M, by just watching memory climb over a week or so.
I want to identify which Thread has the memory leak from within the instance of dllhost I have seen climbing.
Within the Thread there are quite a few DLL's to pin down in regard to the memory leak.
However, next I need to ID the leaking Thread.
??
I want to identify which Thread has the memory leak from within the instance of dllhost I have seen climbing.
Within the Thread there are quite a few DLL's to pin down in regard to the memory leak.
However, next I need to ID the leaking Thread.
??
ASKER
Anyone have a tool that will point to a specific thread that has a memory leak?
i'm not sure that there is any software that can point on memory leak for sure.
how should it know if this is a memory leak or by design?
only programmer with debug tools can know that.
if you find a program that use to much memory until it's crush , you can assume it have memory leak.
how should it know if this is a memory leak or by design?
only programmer with debug tools can know that.
if you find a program that use to much memory until it's crush , you can assume it have memory leak.
ASKER
These tools do the trick!
ASKER
The Sysinternal tools work very well for this solution.
ASKER
.
ASKER
It appears we can.