<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Rendering issues in SolveSpace" href="https://bugs.freedesktop.org/show_bug.cgi?id=108097#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Rendering issues in SolveSpace" href="https://bugs.freedesktop.org/show_bug.cgi?id=108097">bug 108097</a> from <a class="email" href="mailto:sergii.romantsov@globallogic.com" title="Sergii Romantsov <sergii.romantsov@globallogic.com>"> Sergii Romantsov</a> <pre>Sorry, no need in trace at this moment. Bisected: commit aefac10fecc9ec70feb5923ce3200902f67182ba Author: Michel Dänzer <<a href="mailto:michel.daenzer@amd.com">michel.daenzer@amd.com</a>> Date: Tue Sep 4 12:18:19 2018 +0200 loader/dri3: Only wait for back buffer fences in dri3_get_buffer We don't need to wait before drawing to the fake front buffer, as front buffer rendering by definition is allowed to produce artifacts. Fixes hangs in some cases when re-using the fake front buffer, due to it still being busy (i.e. in use for presentation). Cc: <a href="mailto:mesa-stable@lists.freedesktop.org">mesa-stable@lists.freedesktop.org</a> Bugzilla: <a href="https://bugs.freedesktop.org/106404">https://bugs.freedesktop.org/106404</a> Bugzilla: <a href="https://bugs.freedesktop.org/107757">https://bugs.freedesktop.org/107757</a> Tested-by: Olivier Fourdan <<a href="mailto:ofourdan@redhat.com">ofourdan@redhat.com</a>> Reviewed-by: Thomas Hellstrom <<a href="mailto:thellstrom@vmware.com">thellstrom@vmware.com</a>></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>