CODEWITHSUNDEEP
c#iiswindbgdebugdiagdebug-diagnostic-tool
SharpCoder
SharpCoder

Reputation: 19163

Understanding debugDiag report

We are facing an issue with IIS. Our .net 4.5 Web API application hosted on IIS 8.5 stop serving response. if we look at the worker process, request are queued up. Any subsequent request to same url is blocked by IIS.

enter image description here

The memory and CPU usage on the server is under control. Event viewer does not have any error. To investigate the issue, we took the memory dump during the issue and ran it through DebugDiag tool.

The report is indicating some sort of deadlock. 

Detected a serious critical section related problem in w3wp.exe_190920_105811.dmp

Lock at 0x0ef4fcc0 owned by thread 22 is Deadlocked with lock at 0x0ef66ee0 owned by thread 26

Impact analysis

1 critical sections indirectly blocked

Critical Sections 0x0ef4fbe0)

32.69% of threads blocked

(Threads 25 26 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42)

The following functions are involved in the root cause

clr!CrstBase::SpinEnter+92

The following modules are involved in the root cause

C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll from Microsoft Corporation

I am not sure how can I investigate this issue. I have no clue about DebugDiag tool. Please suggest.

Upvotes: 0

Views: 901

Answers (0)

Related Questions