RFR: 8364434: Inconsistent BufferedContext state after GC [v5]
Nikita Gubarkov
ngubarkov at openjdk.org
Wed Aug 13 16:07:45 UTC 2025
On Wed, 13 Aug 2025 13:49:11 GMT, Alexander Zvegintsev <azvegint at openjdk.org> wrote:
>> Although the issues are theoretically possible on any platform when using `BufferedContext`, in practice it is only known to reproduce on Metal.
>> So if we consider only known scenarios, we could as well limit it to macOS. If we consider a theoretical regression scenario, having it on every platform could also be helpful (but not with default XRender mode on Linux of course).
>> But having a non-accelerated pipeline on Linux by default may not be permanent either - when we finish our ongoing Vulkan work under Wakefield, we could eventually make it default. So maybe just leave it for all platforms, wdyt?
>
> I am not opposed to running the test on all platforms.
> Windows and Mac work well, but in the case of Linux and XRender, at this point, we know for certain that the test is not useful and will simply waste 5-15 seconds of CI time on each build.
>
> We can file an issue for Linux to enable the test back on it when we switch to Vulkan (and investigate the XRender case).
Ok, I pushed the update
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/26576#discussion_r2273921180
More information about the client-libs-dev
mailing list