Help with Debug Diag report

We are having problems with an app pool crashing. In some case the
pool just recycles but in others the server just goes off the
network. I am able to reach it by the remote access card and recycle
the pool manually. The server will almost immediately become
available over the production network after that. I am attempting to
use the debug diag tool to troubleshoot but it may be beyond my
abilities to read these things. I am posting the upper part of a
memory report. Any help would be appreciated.

Type Description Recommendation
Warning mscorwks.dll is responsible for 201.14 KBytes worth of
outstanding allocations. The following are the top 2 memory consuming
functions:

mscorwks!EEHeapAlloc+12d: 191.79 KBytes worth of outstanding
allocations.
mscorwks!DebuggerHeap::Alloc+2f: 9.21 KBytes worth of outstanding
allocations. If this is unexpected, please contact the vendor of this
module, Microsoft Corporation, for further assistance with this
issue.
Warning oraclient10.dll is responsible for 7.81 KBytes worth of
outstanding allocations. The following are the top 2 memory consuming
functions:

oraclient10!skplfGetOCIErrcode+c7: 7.81 KBytes worth of outstanding
allocations. If this is unexpected, please contact the vendor of this
module, Oracle Corporation, for further assistance with this issue.
Information
DebugDiag did not detect any known native heap(unmanaged) problems in
w3wp__PID__6056__Date__08_07_2008__Time_10_57_12AM __670__kernel32!
ExitProcess.dmp using the current set of scripts.

On Aug 8, 2:59*pm, greg.san...@ipacc.com wrote:
> We are having problems with an app pool crashing. *In some case the
> pool just recycles but in others the server just goes off the
> network. *I am able to reach it by the remote access card and recycle
> the pool manually. *The server will almost immediately become
> available over the production network after that. *I am attempting to
> use the debug diag tool to troubleshoot but it may be beyond my
> abilities to read these things. *I am posting the upper part of a
> memory report. *Any help would be appreciated.
>
> Type Description Recommendation
> * Warning mscorwks.dll is responsible for 201.14 KBytes worth of
> outstanding allocations. The following are the top 2 memory consuming
> functions:
>
> mscorwks!EEHeapAlloc+12d: 191.79 KBytes worth of outstanding
> allocations.
> mscorwks!DebuggerHeap::Alloc+2f: 9.21 KBytes worth of outstanding
> allocations. If this is unexpected, please contact the vendor of this
> module, Microsoft Corporation, for further assistance with this
> issue.
> * Warning oraclient10.dll is responsible for 7.81 KBytes worth of
> outstanding allocations. The following are the top 2 memory consuming
> functions:
>
> oraclient10!skplfGetOCIErrcode+c7: 7.81 KBytes worth of outstanding
> allocations. If this is unexpected, please contact the vendor of this
> module, Oracle Corporation, for further assistance with this issue.
> * Information
> DebugDiag did not detect any known native heap(unmanaged) problems in
> w3wp__PID__6056__Date__08_07_2008__Time_10_57_12AM __670__kernel32!
> ExitProcess.dmp using the current set of scripts.


Please configure DebugDiag to wait for a Crash and post that report.

A memory report will not help find a crash.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//