Errors associated with a lack of memory is one of the obsession of the Java developer. One of two things, an increase in the volume of allocated memory solves the problem permanently, or it only delayed the day and that's when things get tough!
The good old debugger can not help us for this kind of diganostic, it does not produce useful information about the actual use of memory. It is of course possible to generate a memory dump (with a 'kill -3' under Linux), however, the result can be quite cumbersome to analyze. Recently faced such a problem, I realized that Sun provides with its JDK a set of tools to solve many problems. These tools are available since JDK version 1.5, they are not suportés by Sun and only work on some platforms: Linux, Solaris, Mac OS, not Windows ... Here is a summary of opportunities to diagnose a memory leak problem.
. . . → Read more: OutOfMemoryError: diagnostic tools


