Friends,
We did a hang analysis on a w3wp.exe dump using DebugDiag, but I can't
really tell what might be happening. Somebody grabbed a critical section in
thread 11, and what? SO some other threads are now blocked behind 11, and
we don't even know what 11 was doing really. We are plagued by this sort of
thing right now.
Any thoughts will be very helpfull.
Thanks for taking the time to have a look!
James
Analysis Summary
Type Description Recommendation
Warning Detected possible blocking or leaked critical
section at fd0608 owned by thread 11 in
w3wp.exe__RSWebNETAppPool__PID__3548__Date__11_29_2005__Time_03_02_14PM__512__IIS
Hang Dump.dmp
Impact of this lock
1 critical sections indirectly blocked
( ntdll!LdrpLoaderLock)
67.14% of threads blocked
(Threads 18 23 25 26 27 28 29 30 31 32 33 34 35 36 37 38
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
64 65 66 67 68 69)
The following functions are trying to enter this critical
section
ntdll!RtlReAllocateHeap+2a1
ntdll!RtlAllocateHeap+313
The following module(s) are involved with this critical
section
C:\WINDOWS\system32\ntdll.dll from Microsoft Corporation
One or more of the blocking functions is a heap function.
In most cases this implies leaked critical section caused by heap
corruption. Please follow the steps outlined in the following Knowledge Base
article:
300966 Howto debug heap corruption issues in Internet
Information Services (IIS)
Warning Detected possible blocking or leaked critical
section at 216cfe8 owned by thread 11 in
w3wp.exe__RSWebNETAppPool__PID__3548__Date__11_29_2005__Time_03_02_14PM__512__IIS
Hang Dump.dmp
Impact of this lock
2.86% of threads blocked
(Threads 15 21)
The following functions are trying to enter this critical
section
mscorsvr!Ordinal76+2f0c
The following module(s) are involved with this critical
section
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorsvr.dll
from Microsoft Corporation
The following vendors were identified for follow up based
on root cause analysis
Microsoft Corporation
Please follow up with the vendors identified above
Warning 3 client connection(s) in
w3wp.exe__RSWebNETAppPool__PID__3548__Date__11_29_2005__Time_03_02_14PM__512__IIS
Hang 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
Table Of Contents
w3wp.exe__RSWebNETAppPool__PID__3548__Date__11_29_2005__Time_03_02_14PM__512__IIS
Hang Dump.dmp
Top 5 threads by CPU time
Locked critical section report
Thread report
HTTP Report
COM+ STA ThreadPool Report
Report for
w3wp.exe__RSWebNETAppPool__PID__3548__Date__11_29_2005__Time_03_02_14PM__512__IIS
Hang Dump.dmp
Type of Analysis Performed Hang Analysis
Machine Name JOAN
Operating System Windows Server 2003 Service Pack 1
Number Of Processors 2
Process ID 3548
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 7 day(s) 02:51:18
Process Up-Time 0 day(s) 01:09:57
Top 5 Threads by CPU time
Note - Times include both user mode and kernel mode for each
thread Thread ID: 11 Total CPU Time: 0 day(s) 00:08:07.765 Entry
Point for Thread: mscorsvr!GetAssemblyMDImport+15172
Thread ID: 21 Total CPU Time: 0 day(s) 00:01:29.109
Entry Point for Thread: mscorsvr!GetAssemblyMDImport+15172
Thread ID: 0 Total CPU Time: 0 day(s) 00:00:00.62
Entry Point for Thread: w3wp!wmainCRTStartup
Thread ID: 13 Total CPU Time: 0 day(s) 00:00:00.31
Entry Point for Thread: mscorsvr!CoInitializeCor+a77
Thread ID: 5 Total CPU Time: 0 day(s) 00:00:00.31
Entry Point for Thread: w3tp!THREAD_MANAGER::ThreadManagerThread
Locked critical section report
Critical Section fd0608
Lock State Locked
Lock Count 3
Recursion Count 2
Entry Count 0
Contention Count 4
Spin Count 4000
Owner Thread 11
Owner Thread System ID 1700
Critical Section 216cfe8
Lock State Locked
Lock Count 2
Recursion Count 17
Entry Count 0
Contention Count 2
Spin Count 0
Owner Thread 11
Owner Thread System ID 1700
Critical Section ntdll!LdrpLoaderLock
Lock State Locked
Lock Count 44
Recursion Count 1
Entry Count 0
Contention Count 157
Spin Count 0
Owner Thread 23
Owner Thread System ID 2432
Thread report
Thread 0 - System ID 564
Entry point w3wp!wmainCRTStartup
Create time 11/29/2005 1:52:17 PM
Time spent in user mode 0 Days 0:0:0.46
Time spent in kernel mode 0 Days 0:0:0.15
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
kernel32!WaitForSingleObjectEx+ac
kernel32!WaitForSingleObject+12
w3dt!WP_CONTEXT::RunMainThreadLoop+10
w3dt!UlAtqStartListen+2d
w3core!W3_SERVER::StartListen+bd
w3core!UlW3Start+26e
w3wp!wmain+22a
w3wp!wmainCRTStartup+12b
kernel32!BaseProcessStart+23
Back to Top
Thread 1 - System ID 3464
Entry point ntdll!RtlpTimerThread
Create time 11/29/2005 1:52:17 PM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
