RFR: 8364434: Inconsistent BufferedContext state after GC [v6]

[duke]

On Wed, 13 Aug 2025 16:07:45 GMT, Nikita Gubarkov <ngubarkov at openjdk.org> wrote:

>> For "true" null objects, reset the ref itself to null. Non-null ref with null content means that the object was GC'ed. GC'ed state always behaves as not-equal to the new one, causing corresponding ops to be written into RQ.
>> 
>> Although I could not find practical scenarios where refs other than `validPaintRef` could cause problems, this is generally fragile and potentially problematic for any state object kept in weak ref. Therefore I changed the usage of all weak refs in the same way.
>
> Nikita Gubarkov has updated the pull request incrementally with one additional commit since the last revision:
> 
>   8364434: Inconsistent BufferedContext state after GC
>   
>   Exclude Linux

@YaaZ 
Your change (at version 7d9531617c0f81fbe48ac5ba60516d3dbe43d18f) is now ready to be sponsored by a Committer.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/26576#issuecomment-3184813941