Thanks, it seems a pretty special case and in practice not something most users are going to hit, the fix is trivial though so would be easy to cherry pick for a next upload, https://gitlab.freedesktop.org/glvnd/libglvnd/-/commit/5024e579
** Changed in: libglvnd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1966334 Title: GLVND: Set current thread state to NULL in teardown Status in libglvnd package in Ubuntu: Confirmed Bug description: 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 is not null being not null despite being freed by the destuctor. The change makes the threadState null in the destructor to fix this. Can this make it into the libs in 20.04 LTS? Source package where the issue is encountered: https://launchpad.net/ubuntu/+source/libglvnd/1.3.2-1~ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1966334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
