On Tue, 25 Jan 2022 16:12:11 GMT, Aleksey Shipilev wrote:
> > This looks good, although I don't know whether the additional check for
> > strongReferent != null is needed in clearStrong(). This is all racy code
> > and you have already got a non-null return from getStrong() in case you are
> >
On Mon, 24 Jan 2022 21:32:16 GMT, Peter Levart wrote:
> This looks good, although I don't know whether the additional check for
> strongReferent != null is needed in clearStrong(). This is all racy code and
> you have already got a non-null return from getStrong() in case you are
> calling cle
On Fri, 21 Jan 2022 11:04:22 GMT, Aleksey Shipilev wrote:
>> JDK-8277072 introduced java.io.ClassCache, but there seem to be at least two
>> issues with it:
>> - The cache cannot disambiguate between cleared SoftReference and the
>> accidental passing of `null` value; in that case, the retry
> JDK-8277072 introduced java.io.ClassCache, but there seem to be at least two
> issues with it:
> - The cache cannot disambiguate between cleared SoftReference and the
> accidental passing of `null` value; in that case, the retry loop would spin
> indefinitely;
> - If retry loop would spin
