[Mesa-dev] [Bug 94752] framebuffer from a destroyed drawable is reused when binding the same context to other drawable

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Mar 31 16:15:44 UTC 2016


--- Comment #4 from Guilherme <gqmelo at gmail.com> ---
(In reply to Guilherme from comment #3)
> Just to add that I could also reproduce the bug with direct rendering. Of
> course, with the patch that forces the second dri_drawable to be allocated
> on the same address of the first one

Ok, I was wrong. With direct rendering the bug cannot happen because the
dri_drawable destruction is postponed and is done only after the second
dri_drawable is created.

But then I raise the question should the fix be done on the Xorg server or
Mesa? As this is an implementation detail I think that the fix should be in
Mesa, probably finding a way to make sure that a dri_drawable will no be freed
before the framebuffer associated to it.

You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160331/f3f589b5/attachment.html>

More information about the mesa-dev mailing list