Which Asp.net exceptions can do what?

Question

If I write this code

  protected void Page_Load(object sender, EventArgs e)
    {
        Page_Load(sender, e);
    }

I get the an Error (endless recursion):

and the w3wp.exe process is terminated from task manager.

Fine...

however if i do:

throw new ApplicationException(); //or SystemException();

it appears in just a regular exception page. ( w3wp.exe is still up).

questions :

• what kind of exceptions causing the w3wp.exe to shutdown ?
• what kind of exceptions causing the Application Pool to shutdown ?

p.s. according to what ive just written , please think about the following scenario : i can write a web page , host my site in a farm of sites , and i can terminate the whole w3wp.exe process by creating recursion ..... ( also others will have trouble)...

Can you please answer my questions ?

thanks.

Answer 1

This is most likely the famous StackoverflowException. It's caused by an infinite loop since you're calling the method Page_Load again and again.

From MSDN:

In prior versions of the .NET Framework, your application could catch a StackOverflowException object (for example, to recover from unbounded recursion). However, that practice is currently discouraged because significant additional code is required to reliably catch a stack overflow exception and continue program execution.

Starting with the .NET Framework version 2.0, a StackOverflowException object cannot be caught by a try-catch block and the corresponding process is terminated by default. Consequently, users are advised to write their code to detect and prevent a stack overflow. For example, if your application depends on recursion, use a counter or a state condition to terminate the recursive loop. Note that an application that hosts the common language runtime (CLR) can specify that the CLR unload the application domain where the stack overflow exception occurs and let the corresponding process continue. For more information, see ICLRPolicyManager Interface and Hosting Overview.

You may want to have a look at this answer:

https://stackoverflow.com/a/4802309/284240

Answer 2

The reason for the exception is memory overflow. There are many ways how an application can cause this, there is no point to guess specific scenarios. I imaging good hosting providers should be protected from misbehaving applications.

Answer 3

to add to the answers which alrdy are available. u cant bring down the whole process because every website in a server runs in a seperate AppDomain. so if ur code misbehaves only ur appdomain wud be killed.