-
Notifications
You must be signed in to change notification settings - Fork 326
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
Missing framebuffer images #1446
Comments
I've reached out to @bbilodeau directly for more information. |
It is a no-op to delete objects that do not exist. GAPID uses a shared context for replay - while its fine to delete IDs that do not exist in the current context, they might exist in another. Strip out any IDs that do not belong to the current context in the compat layer. Fixes: google#1446
It is a no-op to delete objects that do not exist. GAPID uses a shared context for replay - while its fine to delete IDs that do not exist in the current context, they might exist in another. Strip out any IDs that do not belong to the current context in the compat layer. Fixes: google#1446
It is a no-op to delete objects that do not exist. GAPID uses a shared context for replay - while its fine to delete IDs that do not exist in the current context, they might exist in another. Strip out any IDs that do not belong to the current context in the compat layer. Fixes: #1446
I still found the issue ,I wonder that the issue is solved or not? |
Hi @ttgdz, The error described in this bug is extremely generic - it pretty much covers all cases where the replay service crashed unexpectedly. If you are encountering this, please can you file a new bug? If it is possible, please can you include a Many thanks, |
Hi @ben-clayton |
After successfully capturing OpenGL ES on a Pixel device to a Mac, most frames are not displayed and the following error is shown: "Couldn't get framebuffer attachment Cause: Failed to connect to device Cause: dial tcp [::1]:50334: getsockopt: connection refused". All of the draw calls for the frames appear to be captured correctly.
The text was updated successfully, but these errors were encountered: