Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Mike — Wed, 30 Nov 2005 15:37:14 GMT

Excellent post.

One question: what performance hits are there when you use a try...catch block but no exception is actually thrown?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Igor Podpalchenko — Wed, 30 Nov 2005 16:19:27 GMT

Good post.

Is the any way to avoid raise of exception in .NET for some section of code ( something like uninterrupted critical section )? As example, how can i ignore ThreadAbortException in Dispose() to minimize a risk that some unmanaged resources will not be closed?

Something like "On Error Resume Next" in С# and without GOTO overheat.

Thanks.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Thu, 01 Dec 2005 12:51:42 GMT

The ThreadAbort exception is a bit tricky, to not say very tricky, since its an asynchrounous exception and can be thrown at any point in your code, so there is really no good answer. The same applies to OutOfMemory exceptions, and the problem is you cant really try/catch here because they could happen in the catch as well.

In 2.0 Critical Finalizers are introduced to help out in this type of situation http://blogs.msdn.com/cbrumme/archive/2004/02/20/77460.aspx, so my recommendation would be to figure out why the threadabort exceptions occurr if they happen very frequently. Normally you would get ThreadAbortExceptions when an ASP.NET request times out or when the application shuts down, in the latter case you should not have to worry about unreleased native resources as they will be released on shutdown. ThreadAbortExceptions caused by Redirect's are also not an issue here since it is not of the asynchronous type (i.e. it is induced on its own thread in a controlled manner). So you can't really write 100% reliable code but with the introduction of CER's and Critical Finalizers things will be much better...

To answer Mike's question... The performance hit of a try/catch without an exception is negligeable.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Igor Podpalchenko — Thu, 01 Dec 2005 13:38:31 GMT

In this case, it isn't possible to write types that are realy safe for multithreaded operations in 1.1. Why does MS not implemented something like this ?:

// Switch to manual exception handling
SwitchToManualExceptions();

// Exception critical code
...
...
...

// Gets raised exceptions
GetLastError();

It's sounds very strange and weird that MS not included those useful features in .NET.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Thu, 01 Dec 2005 16:21:28 GMT

That is exactly what is being introduced in 2.0 with the CER's and Critical Finalizers, but to be perfectly honest with all the issues i have seen, i have very seldom or ever seen problems caused by this. If you don't count problems caused by OutOfMemory exceptions in which case we work on finding the memory hogs and resolve it this way.

Since to my knowledge, ThreadAbort's dont abort unmanaged code you would not get something like an orphaned critical section.

A lot of things have changed in the reliability area for 2.0. If you are interested in reading more... http://blogs.msdn.com/cbrumme/archive/2003/06/23/51482.aspx

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Igor Podpalchenko — Fri, 02 Dec 2005 13:56:28 GMT

Thanks for your comments. I'll try to figure out
how this problem solved in 2.0 .

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

NAVEEN — Tue, 20 Dec 2005 20:25:48 GMT

Hi,
!dumpallexeptions or dae is still not part of the SOS.dll . Is this command still not available for public?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Wed, 21 Dec 2005 12:21:44 GMT

Are you talking about 1.1 or 2.0?

For 1.0 and 1.1. if you use the sos.dll that comes with windbg.exe version 6.5.0003.7 under the clr10 directory it should be there.

use .load clr10\sos to get this version

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Brian Watt — Tue, 24 Jan 2006 22:31:55 GMT

Question: Are finally blocks as expensive as throwing exceptions? If so, are using blocks similarly expensive?

Thanks.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Wed, 25 Jan 2006 10:44:55 GMT

no, the expensiveness is not in the try/catch/finally blocks, those are usually a one instruction jmp (perhaps with a test first). The expensive part is actually throwing the exception, i.e. having an exception handler with no exceptions thrown is very inexpensive.

Just to clarify, It's very important to use exception handlers around code that could cause exceptions... what I wanted to say in my post was that it is equally important to know what your exceptions are so that a) you can eliminate the ones that are not necessary and b) you can act appropriately on the exceptions that really are valid exceptions.

The using statement is just a dev time shortcut to writing the code that would otherwise close or dispose objects etc. so at runtime your IL for doing this manually vs. using the using statement should be approximately the same.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Brandon — Mon, 30 Jan 2006 18:32:56 GMT

Your blogs have been very helpful! So what if I have found the object that is not being released but it has no <root>? It is a class that had a Socket as a member variable, that is getting a SocketException. Is it b/c there is some interop to make socket calls?

thanks.

Exceptions can take you into unnecessary code paths

Jeff Stong — Mon, 06 Feb 2006 20:48:44 GMT

Tim, a fellow Compuware blogger, forwarded me a link to this Microsoft blog entry: Are you aware that...

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Howard — Tue, 21 Feb 2006 13:24:20 GMT

Hi Tess

In the application I work on there are a fair number of ObjectDisposedExceptions. While I'm not expecting any specific help with that as it's my problem, I'm interested to know whether you've come across this before. There's only ever .NET code on the exception thread (I can cope when the exceptions in our code :).

The actual exception is thrown after System.Net.Sockets.Socket.EndReceive() is called (which I assume is all internal to ASP.NET).

Maybe our code isn't waiting around long enough (although I can't see how), or even worse it's a total design fault.

Thanks

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Tue, 21 Feb 2006 14:33:35 GMT

Hi Howard,

That particular problem is a bit hard to track down because it is a very generic error message that can occurr either because the request took too long or because of network issues. And it happens on a different thread as you mention because the calls are often async.

Here is an article with one of the causes
http://support.microsoft.com/?id=884537

I would run !dae -v to dump all the exceptions and see if you get any clues from other exceptions that might have this as an inner exception.

Alternatively generate dumps on clr exceptions as described in my post on 40.000 exceptions and see what else is occurring around the same time.

A third option is to run netmon traces at the same time and see if someone (proxy etc.) might prematurely be shutting down connections for you by sending resets. But as i said, fairly hard to track down.

Thanks,
Tess

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Howard — Wed, 22 Feb 2006 12:25:28 GMT

Hi Tess

Thanks for your reply.

I'm not uploading a file or using SSL when these exceptions occurred so that rules out the that support issue and this happens even when running as localhost.

I think generating dumps as the exceptions happen is the way forward, BTW our application uses an ASP.NET front-end (C#) talking to a ATL 7.0 webservice (mixed mode C++ ISAPI extension dll).

Maybe you could blog about the internal workings of the low level sockets stuff in ASP.NET, there's some stuff I've found in MSDN, but it's not too the depth or detail that you go to.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Howard — Thu, 23 Feb 2006 17:44:34 GMT

One thing I should have mentioned 3 posts up is that the ObjectDisposedException _always_ occurs on the threadpool completion port thread (rather than any of the threadpool workers).

Nine tips for a healthy "in production" ASP.NET application

Notes from a dark corner — Thu, 06 Apr 2006 10:55:28 GMT

The following are based on problems I see people having every day in production ASP.NET systems.
1....

.Net exceptions - Tracking down where in the code the exceptions occurred

If broken it is, fix it you should — Thu, 18 May 2006 17:31:09 GMT

I have written earlier about how to track down exceptions using configuration scripts for adplus.&nbsp;...

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Teagan — Mon, 22 May 2006 12:39:28 GMT

i'd like to know more about orphaned case error in bluej, cause there is no help on their tutorials

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Mon, 22 May 2006 16:37:03 GMT

im sorry to say that i unfortunately know nothing about bluej

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Zero Wing — Thu, 20 Jul 2006 23:27:46 GMT

Bravo!

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

boby — Thu, 27 Jul 2006 03:41:36 GMT

hi tess,
I have a question regarding creation of dump when a specific exception occurs. I noticed that the second TrackCLR.cfg file uses clr10 command. How do i do the same thing using version 2.0 of the clr? THanks

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Fri, 04 Aug 2006 10:50:04 GMT

Boby,

Here is a sample of a config file you can use (make sure you either store sos.dll in the windbg or other accessible directory or change the path for !load):

This will dump on certain exceptions and just !clrstack on others, and you run it using

adplus -c nameofconfigfile.cfg

<ADPlus>
<Settings>
<RunMode> CRASH </RunMode>
<OutputDir> c:\dumps </OutputDir>
<Option> Quiet </Option>

<ProcessName> w3wp.exe </ProcessName>

</Settings>

<PreCommands>

<cmd>r $t1 = 0</cmd>
<cmd>r $t2 = 0</cmd>
<cmd>!load sos</cmd>
<cmd>!threads</cmd>
</PreCommands>

<Exceptions>

<Config>
<Code>AllExceptions</Code>
<Actions1>Log</Actions1>
<Actions2>Void</Actions2>
</Config>

<Config>
<Code>CLR</Code>
<Actions1>Log</Actions1>
<CustomActions1>!soe System.Exception 1;!soe System.InvalidOperationException 2;.if(@$t1==1 | @$t2==1) {.echo 'System.Exception or InvalidOperationException occurred';.dump /ma c:\dumps\myExceptionDump.dmp;gn} .else {.echo 'some other exception occurred';!clrstack;gn}</CustomActions1>
</Config>
</Exceptions>

</ADPlus>

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Ravi — Thu, 10 Aug 2006 22:10:26 GMT

Hi Tess,

Very interesting article, and cleared most of the exceptions in my application using sxe -c "!cen;!clrstack;gn" CLR, but then I found you are using adplus command... Wondering, if you could please explain me on where to write TrackCLR.cfg and how to run adplus.. On the command, if I give adplus, it is saying 'No information available'

thanks

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Fri, 11 Aug 2006 08:53:40 GMT

Hi Ravi,

Adplus is located in the windbg directory. If you copy the text above into TrackClr.cfg and put it in the same directory and then navigate there with the command line, you should be able to run

adplus -c TrackCLR.cfg

However, your way of doing it works perfectly well too, you are just doing it live. The only thing adplus does is to attach with cdb and run sxe -c "!cen;!clrstack;gn" CLR in this case...

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Patrick — Sun, 13 Aug 2006 15:10:55 GMT

Tess,

Great article. Will take me a week to learn it all.

BTW, you are cute!

Patrick

Debugging Production Applications using ADPlus

mattonsoftware.com — Fri, 22 Sep 2006 05:06:34 GMT

ADPlus is a tool that is used to take snapshots of processes in&nbsp;environments where development-time...

ASP.NET 2.0 - Investigating .NET Exceptions with WinDbg (Compilation and Load Exceptions)

If broken it is, fix it you should — Fri, 13 Oct 2006 18:12:42 GMT

I have talked in earlier posts about how to log and debug .net exceptions with WinDBG. All .NET exceptions

Debugging Production Applications using ADPlus

mattonsoftware.com — Wed, 10 Jan 2007 06:47:01 GMT

ADPlus is used to take snapshots of processes in environments where development-time debugging tools

Nine tips for a healthy "in production" ASP.NET application

Notes from a dark corner — Tue, 19 Jun 2007 12:31:42 GMT

The following are based on problems I see people having every day in production ASP.NET systems. 1 .

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Scott — Tue, 29 Jan 2008 18:31:44 GMT

Is there an alternative to using !dae for framework version 2.0?

It's really pissing me off that framework 2.0 has been out forever now and most of the really useful commands available in sos.dll for 1.1 are not available for 2.0. It's making my life very difficult as all of our apps are on 2.0.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Tue, 29 Jan 2008 18:50:02 GMT

Hi Scott,

The best alternative is !dumpheap -type Exception or !dumpheap -type *Exception to dump out all .net exceptions.

You could also do something like

.foreach (ex {!dumpheap -type Exception -short}){!pe ${ex}} if you want to list them all with stacks...

/Tess

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Scott — Tue, 29 Jan 2008 20:05:37 GMT

Wow, that was fast! Yeah, that is basically what I have been doing.

Is there any word on when sos.dll might be updated to have the old functionality again?

I've been trying to track down a particularly nasty problem that has been manifesting itself as an intermittent threadabort exception in one of our production environments. I suspect the underlying error is something different that just happens to be resulting in a threadabort.

We can't consistently reproduce it unfortunately.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Scott — Tue, 29 Jan 2008 20:13:37 GMT

Also the exceptions in my dump don't seem to have stack traces which is not helping...

Another random question for you.... When I left ADPlus attached to the IIS process in QUIET mode to catch ThreadAbort exceptions an end user of the website got a dialog from the browser informing her that a memory dump was occurring.

Is this normal? Is there a way we can prevent that from happening?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Wed, 30 Jan 2008 11:21:39 GMT

sos won't really help you with the fact that they don't have the stacktraces populated:) but that is something you see often for threadaborts when they are due to timeouts or appdomain/process shutdowns.

Only time i've ever seen a stack for a threaabort is the threadaborts that you get from using Response.Redirect where it aborts the current request to avoid running the rest of the page.

I can't say when a certain method will be implemented in sos. Basically the issue is that it is not a straight port because of the changes between debugging .net in 1.1 and 2.0 but sos is constantly being updated.

I can't say why the end user got the messagebox in the browser, to be honest that sounds really really weird to me. It is not somehting that adplus/windbg will do so either it has to be something in the app itself or maybe a jit-debugging box because of a timeout in the browser or something...

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Scott — Wed, 30 Jan 2008 17:08:36 GMT

There were actually some other exceptions in the dump besides the threadabort and none of them had stack traces. Could that be a result of something I'm doing incorrectly when capturing the dumps?

The problem we've got is that we we can not reproduce the issue with any frequency. When it happens the error that is getting reported to the users is a ThreadAbort as the result of a response.redirect, however no part of the process they are executing at the time they see the error is executing a redirect. This makes me think that somehow this error is masking the real underlying error. There have been no entries in the windows eventlog for app/process shutdowns or timeouts at the time the errors have occurred.

Do you have any advice for what might be the best approach to try and find the source of a problem like this?

Catch Exceptions on x64

From Mind To Words — Tue, 29 Apr 2008 06:33:24 GMT

Hello All, Just recently I came across an incident on which a customer saw the following exception in

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Diego Jancic — Tue, 02 Dec 2008 16:45:21 GMT

Amazing post!.

I'm receiving a "Doesn't work with 2.x" when I try to run !cen or something like that. Any ideas?

Thanks!

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Tue, 02 Dec 2008 16:52:00 GMT

!cen doesnt exist in the 2.0 version of sos, there is a config file in the comments of this post that you might be able to use instead. For just looking at an exception use !pe instead of !cen

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Stephan Hartmann — Mon, 06 Apr 2009 11:46:20 GMT

Fine post...

confirms my opionion that throwing exceptions on any and every issue seems not the good practice as it ist always taught, and that the old- fashioned style to check on known issues before relaying on getting an exception (I coded a lot in C) is still up to date.

thanks!

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Richard Turner [MSFT] — Tue, 21 Apr 2009 02:23:00 GMT

Stephan - in .NET, exceptions are vitally important, but (as you implied) should not be abused. The .NET Framework Design Guidelines book provides ample guidance on when exceptions should and shouldn't be used.

The general rule of thumb is that if a given method is unable to complete the task that its name implies, it should throw an appropriate exception.

For example, if File.Open() can't find/open the requested file, it should throw. If CustomerList.AddNewCustomer(...) can't add a new customer, it should throw. etc.

The alternative is a return to the Win32/VB way of doing things - having to check the outcome of every method call each and every time you call them!

Exceptions should reflect a perspective that, from the called method's perspective, it is unable to complete it's action and doesn't know what to do next.

If you have a method that is quite likely to fail, consider using the bool Try<verb><adjective>(...) patterm that returns a bool result but which is also called by the <verb><adjective>(...) method that throws if the Try...() version fails. This way, if you're expecting the operation to fail, you can call the Try...() variation and test the result, but otherwise, call the non-try version and catch exceptions where you're able to back-out of the operation cleanly.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

CullisonX — Tue, 23 Jun 2009 18:28:24 GMT

The original post is specious.

We, the general developer community, didn't encode hundreds or thousands of exceptions that occur over the course of a regular application. Microsoft did. Microsoft's .NET architect(s) created the framework to throw exceptions instead of return result codes or the like, adding even more overhead to the normal operation of a program.

I have *not* thrown over 40,000 exceptions. .NET did. Microsoft did. Don't blame us for a poor architectural choice.

As Richard Turner put it in the previous comment, "The general rule of thumb is that if a given method is unable to complete the task that its name implies, it should throw an appropriate exception."

Even more specious, Turner says, "The alternative is a return to the Win32/VB way of doing things - having to check the outcome of every method call each and every time you call them!"

As opposed to, say, using a try/catch block around every call into .NET? Other than the extreme overhead of using exceptions for normal operating conditions, and the syntax differences between testing error codes versus testing caught exceptions, what's the difference? Give me a good return code any day.

Oh, wait, there's a better way? "If you have a method that is quite likely to fail, consider using the bool Try<verb><adjective>(...) patterm..." *sigh* That's not the actual pattern (<adjective> is probably better served by <property> or <noun>, for example), but nevertheless, it just complicates the API. Now, every operation hopefully has two different calls, one for the exceptioned version, and another for the test version. Either way, I have extra, unnecessary overhead.

The sad thing is that so many Microsoft engineers know why using exceptions is a bad thing, yet somehow this managed to slip into .NET in spite of them. Architecture review, anyone?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

daveblack — Wed, 24 Jun 2009 02:44:23 GMT

The core of the problem is that 98% or developers have no clue what the difference is between an error and an exception. Note that I'm not referring to anyone in these responses - just in general. This is based on my experience in Consulting for 15 years. Some treat exceptions as errors and others treat errors as exceptions. You have to have clear architectural guidelines when developing a Framework that define an error and an exception, when to use each, and how the application should react under each scenario.

A trivial example of an error is entering alphabetic characters in a US phone number field. Ok, so it's a *user* error but you get what I mean. An exceptional case is an "OutOfMemory" exception. Possibly a network timeout, SQL Server problem, etc.

With regard to the comment made by CullisonX about wrapping .NET Framwork calls with TRY/CATCH blocks is hopefully facetious. You never use a TRY/CATCH in a method unless the method cannot continue in an exceptional scenario, needs to do some cleanup, can possibly recover from, or add additional information to the exception such as the state of the data or values when the exception occurred. In other words, don't use TRY/CATCH design IF you EXPECT something could very well fail. This should be treated as an error instead.

In other words, you only use TRY/CATCH if the local method cares about it. Otherwise, you add program overhead just by adding the TRY/CATCH blocks - and especially if you CATCH exceptions and do nothing with them in the place where the CATCH is.

A good Architect, Tech Lead, etc. and Code Reviews should catch this and put the "Kaibash" on it!

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Chris Sizemore — Wed, 24 Jun 2009 04:26:48 GMT

I don't care who ya are - that's just specious.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

MBCDev — Tue, 30 Jun 2009 23:28:11 GMT

Hello,

Excellent post - thank you! I am currently debugging a rather large Visual Basic 6 application (EXE is about 30 Meg) that is doing exactly what you're talking about - I've just started watching the application using WinDbg and am seeing "Unknown exception - code c000008f (first chance)" occurrences rolling in almost constantly.

Since this is unmanaged VB6 code, is it possible to eliminate these sorts of exceptions or are these happening under the sheets of VB6? I have yet to get the pdb file for the app, but I guess I'm just curious as to what I'll find at the heart of all of these exceptions, if anything! Will these point to VB error handlers or something inside of VB6 itself?

Furthermore, is WinDbg really the right tool to do this sort of analysis? We've run the application inside the VB environment enough to know that this is no simple problem with a few lines of code. Something is happening behind the scenes that leads to a problem further on down the line at seemingly random locations, specifically Event ID 1000 Application Errors with no Category and no Faulting Module, or similarly vague reports including the application simply disappearing.

Any help or advice you could provide would be greatly appreciated!

Thanks.

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Tess — Wed, 01 Jul 2009 10:46:48 GMT

c000008f is the standard vb exception if i recall correctly. So if they are handled you probably have some on error resume or on error goto ... in the code.

You can set up an adplus file like this

http://msdn.microsoft.com/en-us/library/cc409011.aspx

(Not sure why it mentions conditional CLR exceptions, i expect there was some typo in there because the CLR exception code is e0434f4d).

Problem is that you may or may not get any good info from the stack depending on where it exceptions out... but it is worth a try.

You should probably change it to have it just show the stack rather than generating full dumps if they are happening very frequently.

Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Exceptions can take you into unnecessary code paths

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Nine tips for a healthy &quot;in production&quot; ASP.NET application

.Net exceptions - Tracking down where in the code the exceptions occurred

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Debugging Production Applications using ADPlus

ASP.NET 2.0 - Investigating .NET Exceptions with WinDbg (Compilation and Load Exceptions)

Debugging Production Applications using ADPlus

Nine tips for a healthy "in production" ASP.NET application

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Catch Exceptions on x64

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

re: Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?

Nine tips for a healthy "in production" ASP.NET application