3 ms·
One could very loosely define a 'leak' as "memory the author didn't expect to be retained past the next few GC cycles". It looks like this tool helps you check
by infogulch 12y ago
One could very loosely define a 'leak' as "memory the author didn't expect to be retained past the next few GC cycles".
It looks like this tool helps you check your assumptions about how long your objects are kept alive.
- joncrocks 12y agoIndeed. In general Java doesn't have memory 'leaks' in the same way as other languages/runtimes, in that things that are kept hanging around are in theory still accessible. It's possible to have things hanging about that are theoretically access able about but will never be accessed again, which is generally what's meant by 'a memory leak' in a Java context.