On Fri, 23 Jan 2026 21:56:06 GMT, Damon Nguyen <[email protected]> wrote:
>This failing test has been untouched for years and has recently started >failing with OOME. If the test hasn’t been changed, does that mean this is a regression in the JDK? > There seems to be a lot of byte arrays that looks like is causing the issue. > To increase stability, I have gone ahead and reduced the endTime duration > from 10 seconds to 5 seconds, which should be enough. What is the root cause of the OOM? A large number of byte arrays are created because the test serializes and deserializes data, which then must be reclaimed by the GC. If the test fails, there are two possible explanations: either there is a memory leak in swing, or there is a bug in the GC. In both cases, the test should not be updated, since it catches a bug in the product. Instead, the root cause of the issue should be investigated. ------------- PR Comment: https://git.openjdk.org/jdk/pull/29395#issuecomment-3794004581
