** Description changed: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. + + [What could go wrong]
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Incomplete Bug description: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. [What could go wrong] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
