Integrated: 8364434: Inconsistent BufferedContext state after GC

[Nikita Gubarkov]

On Thu, 31 Jul 2025 13:31:49 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.

This pull request has now been integrated.

Changeset: 899e13f4
Author:    Nikita Gubarkov <ngubarkov at openjdk.org>
Committer: Laurent Bourgès <lbourges at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/899e13f40a70c98d1d393ba6c3973abcb36e1f00
Stats:     120 lines in 2 files changed: 95 ins; 2 del; 23 mod

8364434: Inconsistent BufferedContext state after GC

Reviewed-by: jdv, azvegint, avu

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

PR: https://git.openjdk.org/jdk/pull/26576