title: What happens to other users if the .NET worker process crashes?
body: <p>My knowledge of how processes are handled by the ASP.Net worker process is woefully inadequate. I'm hoping some of the experts out there can fill me in.</p>
  
  <p>If I crash the worker process with a System.OutOfMemoryException, what would the user experience be for other users who were being served by the same process? Would they get a blank screen? 503 error? </p>
  
  <p>I'm going to attempt to test this scenario with some other folks in our lab, but I thought I would float this out there. I will update with our results.</p>
  
  <p><strong>UPDATE</strong>: Our results varied. If we artificially induced a OOM exception (for example by loading larger and larger PDFs into memory), other threads being served by that worker process would "hang" temporarily and then complete, while others seemingly would never return. Thank you for your responses. </p>