Java Memory Problems Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)
http://blog.dynatrace.com/2009/08/13/java-memory-problems/
Common causes of memory related issues - out of memory, excessive memory usage, and memory leaks in java applications.
Memory Leaks and other memory related problems are among the most prominent performance and scalability problems in Java. Reason enough to discuss this topic in more detail.
.How to detect and avoid memory and resources leaks in .NET applications
Despite what a lot of people believe, it's easy to introduce memory and resources leaks in .NET applications. The Garbage Collector, or GC for close friends, is not a magician who would completely relieve you from taking care of your memory and resources consumption. I'll explain in this article why memory leaks exist in .NET and how to avoid them. Don't worry, I won't focus here on the inner workings of the garbage collector and other advanced characteristics of memory and resources management in .NET. It's important to understand leaks and how to avoid them, especially since they are not the kind of things that is easy to detect automatically. Unit tests won't help here. And when your application crashes in production, you'll be in a rush looking for solutions. So, relax and take the time to learn more about this subject before it's too late. Table of Content * Introduction * Leaks? Resources? What do you mean? * How to detect leaks and find the leaking resources *
.NETでリークする要因。「Events, or the "lapsed listener" issue」は良く目にする。Memory leak patterns in JavaScript
Plugging memory leaks in JavaScript is easy enough when you know what causes them. In this article authors Kiran Sundar and Abhijeet Bhattacharya walk you through the basics of circular references in JavaScript and explain why they can cause problems in certain browsers, especially when combined with closures. After seeing some of the common memory leak patterns you should watch out for, you'll learn a variety of easy ways to work around them.
Memory Leaks in Javascript -> wie wo was warum erklärt dieser Artikel ganz nett