If there is an actual memory leak, it's a problem with your Java runtime environment, as the language is specifically designed to not leak memory.
If there is some amount of memory consumed by the Lookup that's not controlled by the LRU-based cache structure, that could be a problem, but there isn't enough information here to have any idea, since it's unclear whether the lookups are unique or all different, result in positive or negative answers, or anything else. If you have a sample program, please attach it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If there is an actual memory leak, it's a problem with your Java runtime environment, as the language is specifically designed to not leak memory.
If there is some amount of memory consumed by the Lookup that's not controlled by the LRU-based cache structure, that could be a problem, but there isn't enough information here to have any idea, since it's unclear whether the lookups are unique or all different, result in positive or negative answers, or anything else. If you have a sample program, please attach it.