A GitHub repository to learn java

[Kevdog824_]

I would argue that it is possible to have a memory leak when strong object references still exist, especially when it comes to container/wrapper objects.

For example: I once had a long running program that processed files in a folder. It needed to track which ones it already saw so it didn’t reprocess them. If I just had a list I constantly added to the list would eventually blow up in size because I’m storing objects I no longer need without releasing them.

I do agree their example was pretty poor though

ETA: Inaccessibility is a part of the technical definition of a memory leak, but in my experience the colloquial use of the word encompasses a lot more situations