Memory leak in j.l.ThreadLocal

[Martin Buchholz]

On Sat, Oct 26, 2013 at 10:19 PM, Victor Polischuk <victor2 at ukr.net> wrote:

>
> If I did not mess up with the idea reversing weak references then we will
> get small synchronization blocks only on setInitialValue() and remove(). I
> would definitely need a help from someone who knows how to measure
> performance of multi-threading components (have a couple of ideas who could
> it be) but my feelings are telling me that it is a small price.
>

The use case known to me is ReentrantReadWriteLock, which we would like not
to get any slower.