Chapter 5: Application-Specific Problems
A true memory leak is rare; memory hogs are much more common. A memory hog will cause the framework to hold on to more memory than you would anticipate, and looks suspiciously like a memory leak. Regardless of the cause, the symptoms and the pain are the same. Your application may take a performance hit as the system starts paging. You may notice that your application seems to freeze periodically for garbage collection. In the worst-case scenario, your application may crash with
Naturally, different applications share common areas of contention that are often problematic, and we're going take a look at some of the more commonly occurring pitfalls in this chapter. I ...