On 04/25/2017 10:20 PM, Mike Gorchak wrote:
Hi all,
During a quick tests of latest Mesa3D versions at different branches
12.x, 13.x, 17.x we have found that deferred context and surface
destroy doesn't work properly.
What kind of test case are you using, could you share this?
According to docs:
https://www.khronos.org/registry/EGL/sdk/docs/man/html/eglDestroySurface.xhtml
Description
If the EGL surface is not current to any thread, eglDestroySurface
destroys it immediately. Otherwise, surface is destroyed when it
becomes not current to any thread. Furthermore, resources associated
with a pbuffer surface are not released until all color buffers of
that pbuffer bound to a texture object have been released.
Same for context destroy:
https://www.khronos.org/registry/EGL/sdk/docs/man/html/eglDestroyContext.xhtml
Description
If the EGL rendering context is not current to any thread,
eglDestroyContext destroys it immediately. Otherwise, context is
destroyed when it becomes not current to any thread.
Should this behavior be handled at EGL common DRI2 level or DRI2
platform driver level or it should be handled by EGL itself? I can see
some refcounts implemented for EGL surfaces, buteglMakeCurrent seems
don't increment them for surfaces and contexts.
Thanks!
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
