On Tue, 7 Jun 2022 04:15:49 GMT, Sergey Bylokhov <s...@openjdk.org> wrote:
> This is an update of the test which was de-problemlisted > [here](https://github.com/openjdk/jdk/pull/8450). > > Looks like the initial root cause of the issue was related to the last > disposed frame which for some reason was not deleted from the memory, for > that issue, the [next](https://bugs.openjdk.org/browse/JDK-8287707) bug was > reported. > But that change also replaced the usage of weak references by the > Runtime.getRuntime().freeMemory() which is not stable enough to verify the > leak - its return values vary a lot. > > This change returns the usage of weak references and tests only one instance > of TitledBorder which is enough to verify the old > [bug](https://bugs.openjdk.org/browse/JDK-8204963). This pull request has now been integrated. Changeset: bf439f8c Author: Sergey Bylokhov <s...@openjdk.org> URL: https://git.openjdk.java.net/jdk/commit/bf439f8c93157a7f0e6489db2ccc56c5f7210402 Stats: 36 lines in 1 file changed: 5 ins; 18 del; 13 mod 8287876: The recently de-problemlisted TestTitledBorderLeak test is unstable Reviewed-by: psadhukhan, prr ------------- PR: https://git.openjdk.java.net/jdk/pull/9051
