Amir Szekely fe785c2308 Don't ignore maxCapacity if it's not a power of 2 ... Motivation: This fixes bug #2848 which caused Recycler to become unbounded and cache infinite number of objects with maxCapacity that's not a power of two. This can result in general sluggishness of the application and OutOfMemoryError. Modifications: The test for maxCapacity has been moved out of test to check if the buffer has filled. The buffer is now also capped at maxCapacity and cannot grow over it as it jumps from one power of two to the other. Additionally, a unit test was added to verify maxCapacity is honored even when it's not a power of two. Result: With these changes the user is able to use a custom maxCapacity number and not have it ignored. The unit test assures this bug will not repeat itself.		2014-08-31 09:11:01 +02:00
..
src	Don't ignore maxCapacity if it's not a power of 2	2014-08-31 09:11:01 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2014-08-16 03:02:02 +09:00