Comment 0 for bug 1950174
Revision history for this message
| Jean-Baptiste Lallement (jibel) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
b22d8ff
demo site
(Get the code!)
[Description]
This is a request to backport this fix to focal-updates which is affecting users of WSL:
https:/
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.