Help with debugdiag analysis - w3wp hang and using a lot of memory

Help with debugdiag analysis - w3wp hang and using a lot of memory

am 17.09.2007 12:04:44 von mike.varley1

Hi

I've run debugdiag against a worker process that appears to hang and
is also using a large amount of memory. The app pool this processs is
serving is running WSS 2.0. The analysis is below but I'm not sure
where to go next. Can anyone shed any light?

Thanks

Mike


Analysis Summary
Type Description Recommendation
Information The following threads in
Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__PID__7320__465__Manual
Dump.dmp are processing a client request and is/are not fully
resolved. Further analysis of these threads is recommended in order to
determine what may be blocking the request(s).

( 0 )

12.50% of IIS worker threads blocked

100.00% of threads blocked


Warning 2 client connection(s) in
Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__PID__7320__465__Manual
Dump.dmp have been executing a request for more than 90 seconds.
Please see the Client Connections section of this report for more
detailed information about the connection(s).




Analysis Details



Your browser settings are currently prohibiting this report's scripts
from running.
This is preventing some features of this analysis report from
displaying properly. To enable scripts to run, right-click the
security warning above and choose "Allow Blocked Content..." or enable
the "Allow active content to run in files on My Computer*" setting on
the Advanced tab of your "Internet Options" dialog to avoid being
prompted in the future



Table Of Contents
Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__PID__7320__465__Manual
Dump.dmp
Top 5 threads by CPU time
Thread report
Well-Known COM STA Threads Report
HTTP Report

Report for
Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__PID__7320__465__Manual
Dump.dmp



Report for
Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__PID__7320__465__Manual
Dump.dmp
Type of Analysis Performed Hang Analysis
Machine Name Server0119
Operating System Windows Server 2003
Number Of Processors 8
Process ID 7320
Process Image c:\WINNT\system32\inetsrv\w3wp.exe
System Up-Time 16 day(s) 20:06:54
Process Up-Time 2 day(s) 15:57:59


Top 5 Threads by CPU time
Note - Times include both user mode and kernel mode for each thread
Thread ID: 0 Total CPU Time: 00:00:14.296 Entry Point for
Thread: 0x00000000



Thread report

Thread 0 - System ID 11520
Entry point 0x00000000
Create time 09/14/2007 17:24:02
Time spent in user mode 0 Days 00:00:10.390
Time spent in kernel mode 0 Days 00:00:03.906


This thread is processing a client request and is/are not fully
resolved. Further analysis of these threads is recommended in order to
determine what may be blocking the request(s).

Function Source
SharedUserData!SystemCallStub+4
ntdll!NtDelayExecution+c
kernel32!SleepEx+68
kernel32!Sleep+b
EntAPI+13b9
ntdll!LdrpCallInitRoutine+14
ntdll!LdrShutdownProcess+126
kernel32!_ExitProcess+37
kernel32!TerminateProcess
mscorsvr!FailFast+114
mscorsvr!OutOfMemoryCallbackForEE+12
mscorsvr!UnlockedLoaderHeap::UnlockedAllocMem+57
mscorsvr!LoaderHeap::AllocMem+1e
mscorsvr!EEJitManager::NewCodeHeap+8b
mscorsvr!EEJitManager::NewCodeHeap+2c
mscorsvr!EEJitManager::NewCodeHeap+2c
mscorsvr!EEJitManager::allocCode+78
mscorsvr!CEEJitInfo::allocMem+8a
mscorjit!eeAllocMem+1e
mscorjit!emitter::emitEndCodeGen+10b
mscorjit!Compiler::genGenerateCode+9f
mscorjit!Compiler::compCompile+128
mscorjit!Compiler::compCompile+1e8
mscorjit!jitNativeCode+95
mscorjit!CILJit::compileMethod+a2
mscorsvr!CallCompileMethodWithSEHWrapper+52
mscorsvr!JITFunction+2c7
mscorsvr!MakeJitWorker+2bb
mscorsvr!MethodDesc::DoPrestub+498
mscorsvr!PreStubWorker+42
0x001187fe
mscorsvr!DoDeclarativeSecurity+1a


Back to Top

Well-Known COM STA Threads Report
STA Name Thread ID Thread Status Call Status



HTTP report
IIS ATQ worker thread count 8 Thread(s)
Available ATQ worker thread count 8 Thread(s)
Active client connections 20 client connection(s)


Client Connections
Client connection from 10.245.139.194:4325 to 10.245.139.194:80
Host Header server0119-sp:80
GET request for /default.aspx
HTTP Version HTTP/1.1
SSL Request False
Time alive 2 day(s) 15:58:57
QueryString
Request mapped to
HTTP Request State Unknown
Native Request State NREQ_STATE_PROCESS


Client connection from 10.245.139.194:4339 to 10.245.139.194:9975
Host Header 10.245.139.194:9975
GET request for /default.aspx
HTTP Version HTTP/1.1
SSL Request False
Time alive 2 day(s) 15:58:34
QueryString
Request mapped to
HTTP Request State Unknown
Native Request State NREQ_STATE_PROCESS


18 connection(s) waiting for the next request.



Script Summary
Script Name Status Error Code Error Source Error Description Source
Line
CrashHangAnalysis.asp Completed

Re: Help with debugdiag analysis - w3wp hang and using a lot of memory

am 19.09.2007 11:09:14 von David Wang

Please contact McAfee regarding their EntAPI.dll hanging on process
shutdown.

Also, determine if you have sufficient memory for your ASP.Net
application because it's running out of memory, which then ratholes
into this issue.


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





On Sep 17, 3:04 am, mike.varl...@ntlworld.com wrote:
> Hi
>
> I've run debugdiag against a worker process that appears to hang and
> is also using a large amount of memory. The app pool this processs is
> serving is running WSS 2.0. The analysis is below but I'm not sure
> where to go next. Can anyone shed any light?
>
> Thanks
>
> Mike
>
> Analysis Summary
> Type Description Recommendation
> Information The following threads in
> Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__P=
ID=AD__7320__465__Manual
> Dump.dmp are processing a client request and is/are not fully
> resolved. Further analysis of these threads is recommended in order to
> determine what may be blocking the request(s).
>
> ( 0 )
>
> 12.50% of IIS worker threads blocked
>
> 100.00% of threads blocked
>
> Warning 2 client connection(s) in
> Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__P=
ID=AD__7320__465__Manual
> Dump.dmp have been executing a request for more than 90 seconds.
> Please see the Client Connections section of this report for more
> detailed information about the connection(s).
>
> Analysis Details
>
> Your browser settings are currently prohibiting this report's scripts
> from running.
> This is preventing some features of this analysis report from
> displaying properly. To enable scripts to run, right-click the
> security warning above and choose "Allow Blocked Content..." or enable
> the "Allow active content to run in files on My Computer*" setting on
> the Advanced tab of your "Internet Options" dialog to avoid being
> prompted in the future
>
> Table Of Contents
> Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__P=
ID=AD__7320__465__Manual
> Dump.dmp
> Top 5 threads by CPU time
> Thread report
> Well-Known COM STA Threads Report
> HTTP Report
>
> Report for
> Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__P=
ID=AD__7320__465__Manual
> Dump.dmp
>
> Report for
> Hang_Rule_Targets__Date__09_17_2007__Time_09_21_17AM__w3wp.e xe__WSSAPP__P=
ID=AD__7320__465__Manual
> Dump.dmp
> Type of Analysis Performed Hang Analysis
> Machine Name Server0119
> Operating System Windows Server 2003
> Number Of Processors 8
> Process ID 7320
> Process Image c:\WINNT\system32\inetsrv\w3wp.exe
> System Up-Time 16 day(s) 20:06:54
> Process Up-Time 2 day(s) 15:57:59
>
> Top 5 Threads by CPU time
> Note - Times include both user mode and kernel mode for each thread
> Thread ID: 0 Total CPU Time: 00:00:14.296 Entry Point for
> Thread: 0x00000000
>
> Thread report
>
> Thread 0 - System ID 11520
> Entry point 0x00000000
> Create time 09/14/2007 17:24:02
> Time spent in user mode 0 Days 00:00:10.390
> Time spent in kernel mode 0 Days 00:00:03.906
>
> This thread is processing a client request and is/are not fully
> resolved. Further analysis of these threads is recommended in order to
> determine what may be blocking the request(s).
>
> Function Source
> SharedUserData!SystemCallStub+4
> ntdll!NtDelayExecution+c
> kernel32!SleepEx+68
> kernel32!Sleep+b
> EntAPI+13b9
> ntdll!LdrpCallInitRoutine+14
> ntdll!LdrShutdownProcess+126
> kernel32!_ExitProcess+37
> kernel32!TerminateProcess
> mscorsvr!FailFast+114
> mscorsvr!OutOfMemoryCallbackForEE+12
> mscorsvr!UnlockedLoaderHeap::UnlockedAllocMem+57
> mscorsvr!LoaderHeap::AllocMem+1e
> mscorsvr!EEJitManager::NewCodeHeap+8b
> mscorsvr!EEJitManager::NewCodeHeap+2c
> mscorsvr!EEJitManager::NewCodeHeap+2c
> mscorsvr!EEJitManager::allocCode+78
> mscorsvr!CEEJitInfo::allocMem+8a
> mscorjit!eeAllocMem+1e
> mscorjit!emitter::emitEndCodeGen+10b
> mscorjit!Compiler::genGenerateCode+9f
> mscorjit!Compiler::compCompile+128
> mscorjit!Compiler::compCompile+1e8
> mscorjit!jitNativeCode+95
> mscorjit!CILJit::compileMethod+a2
> mscorsvr!CallCompileMethodWithSEHWrapper+52
> mscorsvr!JITFunction+2c7
> mscorsvr!MakeJitWorker+2bb
> mscorsvr!MethodDesc::DoPrestub+498
> mscorsvr!PreStubWorker+42
> 0x001187fe
> mscorsvr!DoDeclarativeSecurity+1a
>
> Back to Top
>
> Well-Known COM STA Threads Report
> STA Name Thread ID Thread Status Call Status
>
> HTTP report
> IIS ATQ worker thread count 8 Thread(s)
> Available ATQ worker thread count 8 Thread(s)
> Active client connections 20 client connection(s)
>
> Client Connections
> Client connection from 10.245.139.194:4325 to 10.245.139.194:80
> Host Header server0119-sp:80
> GET request for /default.aspx
> HTTP Version HTTP/1.1
> SSL Request False
> Time alive 2 day(s) 15:58:57
> QueryString
> Request mapped to
> HTTP Request State Unknown
> Native Request State NREQ_STATE_PROCESS
>
> Client connection from 10.245.139.194:4339 to 10.245.139.194:9975
> Host Header 10.245.139.194:9975
> GET request for /default.aspx
> HTTP Version HTTP/1.1
> SSL Request False
> Time alive 2 day(s) 15:58:34
> QueryString
> Request mapped to
> HTTP Request State Unknown
> Native Request State NREQ_STATE_PROCESS
>
> 18 connection(s) waiting for the next request.
>
> Script Summary
> Script Name Status Error Code Error Source Error Description Source
> Line
> CrashHangAnalysis.asp Completed