-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix eglMakeCurrent and eglDestroySurface validation checks #4652
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there's some failing linux builds with this. Can you take a look at fix those?
Some Linux checks failing with missing GLIBC_2.28 error, so, not related to this PR. |
eglMakeCurrent and eglDestroySurface validation checks fail and exit earlier after device lost were detected, preventing the release of surface and underling swap chain. This makes it impossible to recreate device after device lost. b/329326128
e9b748b
to
acc760f
Compare
@kaidokert some of these failed required checks look infra related. Python tests are failing due to missing python version for instance. |
@kaidokert another ping. I reran the failed checks and still see Java and Python failures that shouldn't be related, but the other required checks passed. |
eglMakeCurrent and eglDestroySurface validation checks fail and exit earlier after device lost were detected, preventing the release of surface and underling swap chain.
This makes it impossible to recreate device after device lost.
b/329326128