Alex Petrov bbed330468 Fix the possible reference leak in Recycler ... Motivation: Under very unlikely (however possible) circumstances, Recycler may leak references. This happens _only_ when the object was already recycled at least once (which means it's got written to the stack) and then taken out again, and never returned. The "never returned" part may be the fault of the user (forgotten `finally` clause) or the situation when Recycler drops the possibly youngest item itself. Modifications: Nullify the item taken from the stack. Result: Reference is cleaned up. If the object is lost, it will be a subject for GC. The rest of Stack / Recycler functionality remains unaffected.		2016-06-01 06:47:43 +02:00
..
src	Fix the possible reference leak in Recycler	2016-06-01 06:47:43 +02:00
pom.xml	Make netty-transport-native-epoll-*-linux-x86_64.jar working in OSGi	2016-05-30 22:04:01 +02:00