Recovering from Memory Leaks and Deadlocks
Web applications have some vulnerabilities where over time their performance can significantly diminish. These vulnerabilities fall into two categories: memory leaks and deadlocks. Both can severely affect the performance of a Web application, even to the point where it comes to a grinding halt. And the .NET CLR offers some substantial help in these areas.
Memory Leaks
Wait a minute, though; .NET applications don’t have memory leaks—right? Yes, in theory that is correct. Unfortunately, though, some developer oversights can cause memory to leak. Take, for instance, an application variable in which user information is stored. What if information is added but never removed? What if the application variable ...
Get Special Edition Using® Microsoft® ASP.NET now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
