Re: Memory leak in ELEvaluator: approaches and alternatives

On Sep 27, 2007, at 9:49 PM  September 27, Bjorn Townsend wrote:
> Makes sense. Might also be worth considering that this code is  
> probably already from an out of date Collections release -- it  
> might be worth comparing it to the current release to see how much  
> has changed.

I've created a new issue for this and submitted a patch. The chief  
differences are in LRUMap, AbstractHashedMap and AbstractLinkedMap;  
nothing that would hurt compatibility that I could see, and the  
change to AbstractHashedMap prevents a memory utilization issue.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43544

Bjorn