.NET Debugging Demos Lab 1: Hang - Review

Web Hosting » Blog Archive » NET Debugging Demos Lab 1: Hang - Review

Web Hosting » Blog Archive » NET Debugging Demos Lab 1: Hang - Review — Wed, 06 Feb 2008 17:25:43 GMT

PingBack from http://blogspace4you.info/?p=11538

Interesting Finds: February 6, 2008

Jason Haley — Wed, 06 Feb 2008 20:26:22 GMT

re: .NET Debugging Demos Lab 1: Hang - Review

Christopher Lewis — Thu, 07 Feb 2008 00:13:18 GMT

Tess -

Your .shell command needs quotes on XP...

.shell -ci "~* e !clrstack" FIND /C "Monitor.Enter"

Link Listing - February 6, 2008

Christopher Steen — Thu, 07 Feb 2008 16:22:51 GMT

Sharepoint Two New Tools for SharePoint Development [Via: axshon ] WPF Visio 2007 to XAML Export Add-in...

Link Listing - February 6, 2008

Christopher Steen — Thu, 07 Feb 2008 16:23:00 GMT

Link Listing - February 6, 2008

re: .NET Debugging Demos Lab 1: Hang - Review

Ole — Fri, 08 Feb 2008 12:30:46 GMT

Brilliant, Tess!

I hope more of these labs are coming. They are a super way to get started with WinDbg.

Thanks,

Ole

re: .NET Debugging Demos Lab 1: Hang - Review

silky — Sat, 09 Feb 2008 13:28:42 GMT

Great stuff.

.NET Debugging Demos Lab 2: Crash - Review

If broken it is, fix it you should — Mon, 11 Feb 2008 16:52:01 GMT

Hi all, I realize that you probably haven't all had a chance to look at the Crash lab yet, considering

.NET Debugging Demos Lab 2: Crash - Review

Noticias externas — Mon, 11 Feb 2008 17:48:49 GMT

Hi all, I realize that you probably haven't all had a chance to look at the Crash lab yet, considering

re: .NET Debugging Demos Lab 1: Hang - Review

baal — Thu, 14 Feb 2008 09:37:45 GMT

Hint: MonitorHeld = 1 for each owner and 2 for each waiter.

A: MonitorHeld here is 85 which means that we have one owner and 84/2=42 waiters

can you give more words to explain it , i can't understand how the number "one owner" and "84/2=42 waiters"

thank you!

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Thu, 14 Feb 2008 10:24:11 GMT

Since the number of monitors held in my case was 85

Index SyncBlock MonitorHeld Recursion Owning Thread Info SyncBlock Owner

20 001c6f74 85 1 0f4a0a70 1ea0 30 02f07964 System.Object

and the owner of the lock holds one monitor, that means that there are 84 monitors left for the waiters (threads waiting for the lock). 84/2 = 42, meaning we have 42 threads waiting for the lock

re: .NET Debugging Demos Lab 1: Hang - Review

Tom — Thu, 14 Feb 2008 11:36:20 GMT

Whenever I refresh the 5 browsers, I get almost the same starttime for each of them (differences are in tenths of seconds) and all of them have an execution time of 5 seconds.

I checked the registry and the registry settings of the reg file have been imported.

I tried this at least 20 times and always get the same result.

When I use tinyget, I get the "desired outcome"; the hang and continue the lab.

For completeness: I am running the labs on a Virtual Machine: Win 2003 Server, dual CPU, 2GB of memory.

Why do I get this different behaviour with the 5 browsers?

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Thu, 14 Feb 2008 12:17:08 GMT

I honestly can't answer that question without looking at the machine, especially since you can repro with tinyget. Only thing i can think of is if perhaps you are getting a cached response in the browser...

if the registry keys weren't set correctly you would have gotten different start times so that is definitely not the case as you mention.

Sorry that i can't give you a better answer:(

.NET Debugging Demos Lab 3: Memory

If broken it is, fix it you should — Fri, 15 Feb 2008 17:10:41 GMT

TGIF, almost time for the weekend... but before you leave, here is lab 3. Todays debugging puzzle will

re: .NET Debugging Demos Lab 1: Hang - Review

Simon — Wed, 20 Feb 2008 03:00:00 GMT

One of the Best exmaples I have seen yet on Windbg in action and practically explained !!!!

.NET Debugging Demos Lab 5: Crash

If broken it is, fix it you should — Wed, 05 Mar 2008 13:20:59 GMT

Last week I published a debugging challenge for Lab 5. It was really interesting to see the results and

re: .NET Debugging Demos Lab 1: Hang - Review

KB — Wed, 12 Mar 2008 06:20:12 GMT

A couple of questions and forgive me if they're remedial in nature. 1. Even with the reg file applied (visual confirmation) my execution times don't escalate. Could someone please tell me what I've done wrong? 2. Does pressing F5 for each browser instance one at a time count as "simultaneously"? If not, what's the best method?Thanks.

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Wed, 12 Mar 2008 11:18:10 GMT

Hi Kb,

Depending on your settings you may need to press ctrl+F5 so that you dont use the cache. Can you post your start times and execution times, or say if your start times seem to be pretty much the same or if there is a 5 second delay on the start time for the 3rd browser?

re: .NET Debugging Demos Lab 1: Hang - Review

KB — Thu, 13 Mar 2008 04:34:01 GMT

Hey Tess,

Found my error. 5 tabs open in 1 browser does not equal 5 browsers. My bad. Execution times now escalate as they should. Thanks for taking the time!

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Thu, 13 Mar 2008 09:55:09 GMT

excellent

re: .NET Debugging Demos Lab 1: Hang - Review

KB — Fri, 14 Mar 2008 04:58:42 GMT

Hey Tess,

Just finished this one. Such great information! I really appreciate you doing this for us! On to the next one.

Something I noticed, or actually did, that caused me some pain and that is, I copied and pasted adplus –hang –pn w3wp.exe –quiet into the command window and attempted to run it. Kept getting back "Errors found reading external arguments:". I hammered on it for hours only to discover that I must actually type it in. Copy and paste no worky. Could the command window have picked up some kind of wacky, hidden character as a result of this? Can't say that I've ever seen this type of behavior before in cmd. At any rate, just thought I'd mention it in case there are other "greenhorns" like me out there.

Take care and happy Friday!

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Fri, 14 Mar 2008 10:03:11 GMT

Hi KB,

yeah, it probably did, if you copy adplus -hang -pn w3wp.exe -quiet into some tools (like outlook or word) they sometimes have autoformat settings that makes the minus sign into a long dash which is why you get this error.

I am thinking that livewriter or html rendering does the same thing.

.NET Debugging Demos Lab 7: Memory Leak - Review

If broken it is, fix it you should — Thu, 03 Apr 2008 15:33:39 GMT

We have reached the end of the .NET Debugging Demos series. And we are going to end it with a review

re: .NET Debugging Demos Lab 1: Hang - Review

baal — Fri, 04 Apr 2008 10:42:17 GMT

after I got the dump file(2 files), I run the follow cmd,got error:

-----------------1------------------------------------

0:000> ~* e!clrstack

Failed to find runtime DLL (mscorwks.dll), 0x80004005

Extension commands need mscorwks.dll in order to have something to do.

>>>try lmvm mscor*, no mscorwks.dll loaded why?

----------------2-----------------------

0:019> !clrstack

OS Thread Id: 0x13a0 (19)

Failed to start stack walk: 80004005

why?

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Fri, 04 Apr 2008 10:48:38 GMT

That means that the process you got a dump of has not been serving any asp.net requests, or processed any .net code.

re: .NET Debugging Demos Lab 1: Hang - Review

Matt — Fri, 04 Apr 2008 16:49:30 GMT

I can't get Adplus to work. I tried copy/pasting into the command prompt and it didn't work. Gives me "Errors found reading external arguments"

When I typed it in manually, it tells me w3wp.exe is not running(which it is not), but I can still access the site just fine.

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Fri, 04 Apr 2008 17:09:35 GMT

for the "errors found reading external arguments" . Sometimes - is formatted as doubledash so that is why you are getting that.

For the second problem you are probably looking at a cached copy of the page when you access the site, try Ctrl+F5 or close down the browser to get a fresh copy rather than a cached one, that should start up the w3wp.exe process again

re: .NET Debugging Demos Lab 1: Hang - Review

baal — Sat, 05 Apr 2008 11:39:23 GMT

"2. Open up 5 browsers, all browsing to this site and refresh them simultaneously" -------> I can't click as fast as possible, when i click refesh the 3th borwse, the 1th borwse is ready. I got the cache on the 3th borwse.(I run the reg file)

re: .NET Debugging Demos Lab 1: Hang - Review

baal — Sat, 05 Apr 2008 11:45:02 GMT

"tinyget -srv:localhost -uri:/BuggyBits/FeaturedProducts.aspx -threads:30 -loop:50 " ---> does this cmd run very slow or very fast? loop:50 is very fast?

i prepare two cmd windows, 1th is for tinyget, 2th is for "adplus –hang –pn w3wp.exe –quiet" , I hit enter in the 1th cmd window, before the prompt appear, I hit enter in the 2th cmd window. am I right? but I got the error of above Comment.

re: .NET Debugging Demos Lab 1: Hang - Review

baal — Sat, 05 Apr 2008 12:39:12 GMT

Hi Tess

0:026> .shell -ci "~* e !clrstack" FIND /C "Monitor.Enter"

/c: /c: not found

.shell: Process exited

? why

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Mon, 07 Apr 2008 10:57:00 GMT

Baal, for the error, see the answer to the comment...

re, clicking as fast as possible, try putting the pages side by side, each page should take 5 seconds to load.

For the .shell, not sure where /c: /c: is comming from the command looks right

re: .NET Debugging Demos Lab 1: Hang - Review

J.W. — Fri, 22 Aug 2008 06:41:38 GMT

" the owner of the lock holds one monitor, that means that there are 84 monitors left for the waiters (threads waiting for the lock). 84/2 = 42, meaning we have 42 threads waiting for the lock"

Can you explain why each waiting thread has two monitors?

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Fri, 22 Aug 2008 17:53:38 GMT

To be honest I haven't really looked into the details. I just know that this is always the case from looking at the number of waiting threads and the number of monitors that syncblk shows

re: .NET Debugging Demos Lab 1: Hang - Review

J.W. — Sun, 24 Aug 2008 04:16:14 GMT

Thank you for your reply. I may ask a too simple question. If somebody asks me why 1+1=2, I won't have any answer either. I learned a lot from your blogs, by far the best blog I have ever read.

re: .NET Debugging Demos Lab 1: Hang - Review

James — Tue, 07 Oct 2008 01:09:04 GMT

Hey Tess,

What's the difference between "~* e !clrstack" and "!clrstack"?

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Tue, 07 Oct 2008 08:52:26 GMT

!clrstack shows you the .net stack of the current thread. ~* e !clrstack shows you the .net stacks of all threads.

~ means thread

* means all

e means evaluate

re: .NET Debugging Demos Lab 1: Hang - Review

Tony WU — Tue, 07 Oct 2008 17:46:32 GMT

You should use the aspnet_wp.exe on XP(IIS 5.X) to capture the dump

adplus -hang -pn aspnet_wp.exe -quiet

【翻译】Lab2. Hang调试

Wencui — Fri, 16 Jan 2009 08:57:11 GMT

前几天我翻译了Tess debug系列的第一篇文章以及和大家介绍了一些debugger tools的基本命令。今天我们将一起讨论Tess关于debug 系列的第二篇文章。Tess在每个系列中都使用了问题结果的结构，为了简化，我将把问题和结果一起给大家。此外，大家在自己机器上重现这些问题的时候，由于机器的差异，许多问题的结果都可能和Tess的不一样，这个不要紧，只要大家能够掌握原理就可以了。

re: .NET Debugging Demos Lab 1: Hang - Review

Hari Shankar Chavali — Wed, 11 Mar 2009 19:41:50 GMT

Awesome. The only resource I have ever found on windows debugging that is very lucid and easy to follow. Few suggestions. When I did the first lab, I did not know a lot about some of the command..for example..~ means thread,~. current thread, ~* all htreads in the process k means stack trace and e means commands enter into memory and so on..some basic tutorial of sorts on this as a first tutorial might help.. ofcourse it was not difficult to read from help...I suggest you write a book..Thank you

re: .NET Debugging Demos Lab 1: Hang - Review

Petter — Mon, 20 Apr 2009 12:17:25 GMT

Hi Tess,

I've just started your labs series. I am using Windows 2008 Server x64 and WinDbg 6.11.0001.404.

My problem is that the stack traces are a bit different on this environment, and the most important stuff is not in the trace, e.g. the managed stack looks like this:

OS Thread Id: 0x11b4 (21)

Child-SP RetAddr Call Site

0000000005fcdf80 000007ff001f151b DataLayer.GetFeaturedProducts()

0000000005fce010 000007fef5433ec9 FeaturedProducts.Page_Load(System.Object, System.EventArgs)

0000000005fce0a0 000007feedb36aea System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr, System.Object, System.Object, System.EventArgs)

0000000005fce0d0 000007feedb2d2c4 System.Web.Util.CalliEventHandlerDelegateProxy.Callback(System.Object, System.EventArgs)

0000000005fce100 000007feedb2d322 System.Web.UI.Control.OnLoad(System.EventArgs)

0000000005fce140 000007feedb298ac System.Web.UI.Control.LoadRecursive()

0000000005fce190 000007feedb28db0 System.Web.UI.Page.ProcessRequestMain(Boolean, Boolean)

0000000005fce260 000007feedb28cdb System.Web.UI.Page.ProcessRequest(Boolean, Boolean)

0000000005fce2c0 000007feedb28c70 System.Web.UI.Page.ProcessRequest()

0000000005fce320 000007ff001f03e9 System.Web.UI.Page.ProcessRequest(System.Web.HttpContext)

0000000005fce380 000007feedb30117 ASP.featuredproducts_aspx.ProcessRequest(System.Web.HttpContext)

0000000005fce3b0 000007feedaf449b System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

0000000005fce460 000007feedb02215 System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)

0000000005fce500 000007feedaf3553 System.Web.HttpApplication+ApplicationStepManager.ResumeSteps(System.Exception)

0000000005fce5b0 000007feedaf7874 System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(System.Web.HttpContext, System.AsyncCallback, System.Object)

0000000005fce610 000007feedaf745c System.Web.HttpRuntime.ProcessRequestInternal(System.Web.HttpWorkerRequest)

0000000005fce6a0 000007feedaf608c System.Web.HttpRuntime.ProcessRequestNoDemand(System.Web.HttpWorkerRequest)

0000000005fce6e0 000007fefa342322 System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr, Int32)

As you see, it's missing the line with Monitor.Enter.

Do you know what can cause this?

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Mon, 20 Apr 2009 12:35:52 GMT

Not sure why it is missing to be honest, might be a difference of framework version... how does the native stack look (kb 2000)?

re: .NET Debugging Demos Lab 1: Hang - Review

Petter — Tue, 21 Apr 2009 11:27:03 GMT

This is what returned by kb 2000:

0:000> kb 2000

RetAddr : Args to Child : Call Site

00000000`77b3c730 : 00000000`00000000 000007fe`fb6d7efb 00000000`00000000 000007fe`fc2f15c0 : ntdll!ZwWaitForSingleObject+0xa

000007fe`fc2f3d04 : 00000000`00000148 00000000`ffa65de0 00000000`00000000 00000000`00000148 : kernel32!WaitForSingleObjectEx+0x9c

00000000`ffa62332 : 00000000`fffffffe 00000000`00000001 00000000`001462a0 00000000`0000008c : w3wphost!AppHostInitialize+0x280

00000000`ffa63b09 : 00000000`00000000 00000000`ffa63c7d 00000000`00000000 00000000`00000000 : w3wp!wmain+0x45e

00000000`77b3466d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : w3wp!PerfStopProvider+0x199

00000000`77c68791 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd

00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d

I think this is more like what you are looking for:

0:000> ~26 kb 2000

RetAddr : Args to Child : Call Site

00000000`77b3c648 : 00000000`00000000 00000000`08ed43d1 00000000`ffffffff 00000000`0264e490 : ntdll!NtDelayExecution+0xa

000007fe`fa5c897d : 00000000`00000000 00000000`00000001 ffffffff`fd050f80 00000000`0264e490 : kernel32!SleepEx+0x84

000007fe`fa193af5 : 00000000`02577870 000007fe`fa2ca082 00000000`00001388 00000000`00001388 : mscorwks!EESleepEx+0x2d

000007fe`fa7747a9 : 06000000`00000001 00000001`bfadecf0 00000001`bfae0130 00000000`00001388 : mscorwks!Thread::UserSleep+0x71

000007ff`001f16c9 : 000007fe`00001388 00000000`00000000 000007fe`ed90b180 000007fe`ee1e0abd : mscorwks!ThreadNative::Sleep+0xf9

000007ff`001f14fb : 00000001`3fa965a0 00000000`00000003 00000000`00000000 00000000`00000000 : 0x7ff`001f16c9

000007fe`f5e33ec9 : 00000001`ffa7a8e0 00000001`bfae2500 00000001`bfae1978 000007fe`eda94078 : 0x7ff`001f14fb

000007fe`edb36aea : 00000001`bfae0828 000007fe`ee2354d0 00000001`bfadecf0 00000001`3faef0c0 : System_Web_RegularExpressions_ni+0x33ec9

000007fe`edb2d2c4 : 00000000`00000000 00000001`bfae0828 00000001`bfadecf0 00000001`bfae0828 : System_Web_ni+0x2a6aea

000007fe`edb2d322 : 00000001`bfae0130 000007fe`edaf649b 00000001`bfadecf0 00000000`00000000 : System_Web_ni+0x29d2c4

000007fe`edb298ac : 48cb906b`7f178aad 000007fe`edbf9388 00000001`bfadecf0 00000001`3fbf2508 : System_Web_ni+0x29d322

000007fe`edb28db0 : 00000001`bfadecf0 00000001`ffa7c801 00000001`bfada101 000007fe`f156c8ff : System_Web_ni+0x2998ac

000007fe`edb28cdb : 00000001`bfadecf0 00000001`ffa7c8f8 00000001`bfad9001 00000000`00000003 : System_Web_ni+0x298db0

000007fe`edb28c70 : 00000001`bfadecf0 000007fe`f1c04be0 00000001`bfadf090 000007fe`edb06625 : System_Web_ni+0x298cdb

000007ff`001f03c9 : 00000001`bfada8f0 00000001`bfad8f10 00000001`bfaddf10 00000000`053ce7e0 : System_Web_ni+0x298c70

000007fe`edb30117 : 00000000`053ce780 000007fe`edaf649b 00000000`4190ab00 000007fe`edaf649b : 0x7ff`001f03c9

000007fe`edaf449b : 00000001`7fb14678 000007fe`edb02ae9 00000000`00000000 ef000003`80000008 : System_Web_ni+0x2a0117

000007fe`edb02215 : 00000001`bfad9f10 00000001`bfaddf10 00000000`053ce938 000007fe`edae2be2 : System_Web_ni+0x26449b

000007fe`edaf3553 : 00000001`bfadda50 00000000`00000000 00000001`bfad8f10 000007fe`edaf649b : System_Web_ni+0x272215

000007fe`edaf7874 : 000007fe`edc80bb0 000007fe`f15782f5 00000000`053cee18 00000000`00000000 : System_Web_ni+0x263553

000007fe`edaf745c : 00000001`7fb144a0 00000001`bfad7048 00000000`00000035 00000000`00000005 : System_Web_ni+0x267874

000007fe`edaf608c : 00000000`ffffffff 00000000`0296eeb0 00000000`053cee18 00000000`00000002 : System_Web_ni+0x26745c

000007fe`fa342322 : 00000001`3faad3a0 00000000`0296eeb0 00000000`00000002 ffffffff`fffffffe : System_Web_ni+0x26608c

000007fe`fa243bb3 : 00000000`053cecf0 00000000`053cedc0 ffffffff`fffffffe 00000000`00000000 : mscorwks!CallDescrWorker+0x82

000007fe`fa2651f8 : 00000000`053cee00 00000000`053cf3c0 00000000`00000003 00000000`00000003 : mscorwks!CallDescrWorkerWithHandler+0xd3

000007fe`fa265563 : 00000000`0199fc70 00000000`00081800 00000001`00000000 000007fe`00000004 : mscorwks!ForwardCallToManagedMethod+0x160

000007fe`fa284738 : 00000000`0258dcd0 00000000`0264e490 00000000`02930158 00000000`02930220 : mscorwks!COMToCLRWorkerBody+0x35b

000007fe`fa24c8ae : 00000000`00000000 000007ff`ffee6000 00000000`053cf400 00000000`00000000 : mscorwks!COMToCLRWorkerDebuggerWrapper+0x50

000007fe`fa34249e : 00000000`0264e490 00000000`053cf400 ffffffff`ffffff00 00000000`00000000 : mscorwks!COMToCLRWorker+0x366

00000642`fff58293 : 00000000`0129fda0 00000000`0296eeb0 00000000`00000002 00000000`053cf460 : mscorwks!GenericComCallStub+0x5e

00000642`fff58633 : 00000000`00000000 00000000`0296eeb0 00000000`01dbd9a0 00000000`00000001 : webengine!HttpCompletion::ProcessRequestInManagedCode+0x2a3

00000642`fff9abf4 : 000007fe`fa957c78 00000000`00000001 00000642`fff9abd0 00000000`00000001 : webengine!HttpCompletion::ProcessCompletion+0x63

000007fe`fa1cdc77 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : webengine!CorThreadPoolWorkitemCallback+0x24

000007fe`fa1e289a : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`0264e490 : mscorwks!UnManagedPerAppDomainTPCount::DispatchWorkItem+0x157

000007fe`fa15f0ac : 00000000`00000000 00000000`00000000 00000000`053cfda0 00000000`00000000 : mscorwks!ThreadpoolMgr::WorkerThreadStart+0x1ba

00000000`77b3466d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mscorwks!Thread::intermediateThreadProc+0x78

00000000`77c68791 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd

00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d

And the managed counterpart:

0:000> ~26 e! clrstack

OS Thread Id: 0x1014 (26)

Child-SP RetAddr Call Site

00000000053ce380 000007ff001f14fb DataLayer.GetFeaturedProducts()

00000000053ce410 000007fef5e33ec9 FeaturedProducts.Page_Load(System.Object, System.EventArgs)

00000000053ce4a0 000007feedb36aea System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr, System.Object, System.Object, System.EventArgs)

00000000053ce4d0 000007feedb2d2c4 System.Web.Util.CalliEventHandlerDelegateProxy.Callback(System.Object, System.EventArgs)

00000000053ce500 000007feedb2d322 System.Web.UI.Control.OnLoad(System.EventArgs)

00000000053ce540 000007feedb298ac System.Web.UI.Control.LoadRecursive()

00000000053ce590 000007feedb28db0 System.Web.UI.Page.ProcessRequestMain(Boolean, Boolean)

00000000053ce660 000007feedb28cdb System.Web.UI.Page.ProcessRequest(Boolean, Boolean)

00000000053ce6c0 000007feedb28c70 System.Web.UI.Page.ProcessRequest()

00000000053ce720 000007ff001f03c9 System.Web.UI.Page.ProcessRequest(System.Web.HttpContext)

00000000053ce780 000007feedb30117 ASP.featuredproducts_aspx.ProcessRequest(System.Web.HttpContext)

00000000053ce7b0 000007feedaf449b System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

00000000053ce860 000007feedb02215 System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)

00000000053ce900 000007feedaf3553 System.Web.HttpApplication+ApplicationStepManager.ResumeSteps(System.Exception)

00000000053ce9b0 000007feedaf7874 System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(System.Web.HttpContext, System.AsyncCallback, System.Object)

00000000053cea10 000007feedaf745c System.Web.HttpRuntime.ProcessRequestInternal(System.Web.HttpWorkerRequest)

00000000053ceaa0 000007feedaf608c System.Web.HttpRuntime.ProcessRequestNoDemand(System.Web.HttpWorkerRequest)

00000000053ceae0 000007fefa342322 System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr, Int32)

Thanks!

And a tip :)

Apache (the web server) has a nice small load test tool called apache bench (ab). It has similar functionality as tinyget but it has a friendlier command line interface (http://httpd.apache.org/docs/2.0/programs/ab.html). It has a Windows port.

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Tue, 21 Apr 2009 11:36:04 GMT

Ok, that explain why there was no monitor enter, this thread is sitting in a sleep, not waiting for a lock

re: .NET Debugging Demos Lab 1: Hang - Review

Petter — Tue, 21 Apr 2009 11:40:01 GMT

Coincidentally, thread 26 owned the lock, here's another native stack trace which looks more like your example:

0:000> ~27 kb

RetAddr : Args to Child : Call Site

00000000`77b3b362 : 00000000`00000030 00000000`05a4dad0 00000000`05a4d860 00000000`00000000 : ntdll!ZwWaitForMultipleObjects+0xa

000007fe`fa181299 : 00000000`055d0480 00000000`00000000 00000000`00000000 000007fe`fa18512f : kernel32!WaitForMultipleObjectsEx+0x10b

000007fe`fa1869bd : ffffffff`00000001 00000000`02577888 00000000`055d0480 000007fe`fa1998b0 : mscorwks!WaitForMultipleObjectsEx_SO_TOLERANT+0xc1

000007fe`fa28af55 : 00000000`00000000 00000000`02577888 00000000`00000000 00000000`ffffffff : mscorwks!Thread::DoAppropriateAptStateWait+0x41

000007fe`fa2b2724 : 00000001`00000000 000007fe`fa6f234d 00000000`02577888 000007fe`00000000 : mscorwks!Thread::DoAppropriateWaitWorker+0x191

000007fe`fa1d2266 : 00000000`05a4dae8 000007fe`00000001 00000000`ffa7dd00 00000000`00000000 : mscorwks!Thread::DoAppropriateWait+0x5c

000007fe`fa164251 : 00000000`02577870 00000000`ffffffff 00000000`055d0480 00000000`02577870 : mscorwks!CLREvent::WaitEx+0xbe

000007fe`fa2ca082 : 00000000`02577870 00000000`02577870 00000000`ffffffff 00000000`00000000 : mscorwks!AwareLock::EnterEpilog+0xc9

000007fe`fa1a49fb : 00000000`00000007 00000000`ffffffff 00000000`01e01900 00000000`02577870 : mscorwks!AwareLock::Enter+0x72

000007fe`fa74970f : 00000000`055d0480 00000000`05a4de10 00000000`05a4dcb8 00000000`055d0480 : mscorwks!AwareLock::Contention+0x1fb

000007ff`001f16be : 00000000`02577870 00000000`00000000 000007fe`ed90b180 000007fe`ee1e0abd : mscorwks!JITutil_MonContention+0xdf

000007ff`001f14fb : 00000001`3fa965a0 00000000`00000003 00000000`00000000 00000000`00000000 : 0x7ff`001f16be

000007fe`f5e33ec9 : 00000001`ffa7a8e0 00000000`ffa7fa10 00000000`ffa7ee88 000007fe`eda94078 : 0x7ff`001f14fb

000007fe`edb36aea : 00000000`ffa7dd38 000007fe`ee2354d0 00000000`ffa7c200 00000001`3faef0c0 : System_Web_RegularExpressions_ni+0x33ec9

000007fe`edb2d2c4 : 00000000`00000000 00000000`ffa7dd38 00000000`ffa7c200 00000000`ffa7dd38 : System_Web_ni+0x2a6aea

000007fe`edb2d322 : 00000000`ffa7d640 000007fe`edaf649b 00000000`ffa7c200 00000000`00000000 : System_Web_ni+0x29d2c4

000007fe`edb298ac : 48cb906b`7f595e0d 000007fe`edbf9388 00000000`ffa7c200 00000001`3fbf2508 : System_Web_ni+0x29d322

000007fe`edb28db0 : 00000000`ffa7c200 00000001`ffa7c801 00000000`ffa77901 000007fe`f156c8ff : System_Web_ni+0x2998ac

000007fe`edb28cdb : 00000000`ffa7c200 00000001`ffa7c8f8 00000000`ffa76801 00000000`00000003 : System_Web_ni+0x298db0

000007fe`edb28c70 : 00000000`ffa7c200 000007fe`f1c04be0 00000000`ffa7c5a0 000007fe`edb06625 : System_Web_ni+0x298cdb

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Tue, 21 Apr 2009 11:49:59 GMT

ok, so in that case i would recommend that you look at the native stack to see the locks, not sure why monitor.enter is not showing up there in the managed callstack,

in reality a call to thread.sleep should also have shown up in the managed stack for thread 26

re: .NET Debugging Demos Lab 1: Hang - Review

nipam — Thu, 28 May 2009 04:18:18 GMT

Tess, We are thankful to you for what you are doing for development community. Why don't you think of writing books? I think soon you will see your books in top 10 selling books list on Amazon :)

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Thu, 28 May 2009 12:15:17 GMT

Thanks nipam, I'm humbled your comment:)

I have thought about writing a book a couple of times but there are already a few other really good books out there on .net debugging and i kinda like to be able to write in a blog format, just writing whatever pops into your head:)

re: .NET Debugging Demos Lab 1: Hang - Review

sunny 2009 — Wed, 08 Jul 2009 18:42:02 GMT

Hi Tess, I went through comments listed above and found a Comment by Matt where w3wp process was not able to start but could open the site just fine.

1. I am facing a similar problem, where w3wp.exe process is not starting but can access the site.

2. Tried opening new browsers and used cntrl+F5 before opening the featured products in new browser. I get Browser1 : 5 sec: Browser2 : 9 sec ..... and browser 3,4,5 onwards 9 sec

Can you write how to start w3wp.exe process and also to see the required page delays when new browser is opened

re: .NET Debugging Demos Lab 1: Hang - Review

Tess — Thu, 09 Jul 2009 10:08:37 GMT

if you can browse the page but the w3wp.exe process is not started that probably means that you are running on xp or similar where you have an aspnet_wp.exe process instead. (in that case, just replace w3wp.exe with aspnet_wp.exe anywhere it is mentioned in the instructions)

Regarding the time delay, it looks like you havent run the internetconnections.reg file to allow more than 2 concurrent connections.