Indeed. 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

Indeed. 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.