An unhandled application exception could crash an app pool, as could a
deadlock, as could a process consuming excessive memory or a threaded app
not written well, making network calls, access violations, infinite loops.
To be truthful theres a million reasons why an app pool might hang up.
Any app pool crash through would see the app pool recycle and restart
itself - its not the end of the world in a laod balanced farm but on shared
hosting could be rather problematic if the ISP have too many web apps
sharing the same app pool. Ask your ISP to dedicate an app pool to you
until you get it sorted out, then only you suffer if it crashes and look at
using some sort of memory profiling tool, or test tool like nunit to find
out what the problem is.
Worth having aread of this
http://blogs.msdn.com/david.wang/ar...Understand_and_Diagnose_an_AppPool_Crash.aspx
Regards
John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog