[Desktop-packages] [Bug 1966334] Re: GLVND: Set current thread state to NULL in teardown

I do think it is worth mentioning that since it is a in issue that shows up in the Vulkan CTS, it is likely that it will also show up in other applications. It may also occur on other platforms, but the two I listed are the only ones that I confirmed the issue is reproducing on. -- You received

[Desktop-packages] [Bug 1966334] Re: GLVND: Set current thread state to NULL in teardown

The bug was observed running the Vulkan CTS on an Nvidia Jetson AGX Xavier Developer Kit and on a Jetson AGX Orin Developer Kit. Running the testcase dEQP-VK.api.object_management.alloc_callback_fail.instance without an X display should cause the double free to occur. I confirmed that this is a

[Desktop-packages] [Bug 1966334] [NEW] GLVND: Set current thread state to NULL in teardown

Public bug reported: A new fix has been merged into the libglvnd repo at https://gitlab.freedesktop.org/glvnd/libglvnd This change fixes an issue where if eglReleaseThread gets externally called after the EGL destructor, a double free occurs due to the threadState that eglReleaseThread checks