This is most likely caused by a server error. Sometimes when an error is thrown during initialization the app status page fails to handle it properly and thus the application appears to have been stuck on the page.
Next time it happens instead of restarting the application pool try simply refreshing the page and the actual error should appear shedding a bit more light on what has gone wrong.
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal
and vote to affect the priority of the items