<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Protocol: wl_buffer.release is racy" href="https://bugs.freedesktop.org/show_bug.cgi?id=75303#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Protocol: wl_buffer.release is racy" href="https://bugs.freedesktop.org/show_bug.cgi?id=75303">bug 75303</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>(In reply to Jonas Ådahl from <a href="show_bug.cgi?id=75303#c10">comment #10</a>) > The only issue would be that it's hard for the client (especially EGL) to > know when it can rely on the multi-surface case to work properly, especially > if it's not possible to get the version of the bound (wl_surface) proxy (or > the newest version supported by the server). EGL should never hit this. App cannot get the wl_buffer used by EGL, and EGL won't push the same wl_buffer to multiple surfaces or without waiting for release. How to know that the refcounting actually works, that's an important question. For EGL it should be irrelevant, but other libraries might perhaps care. Looking at the wl_proxy_get_version() issue would be well worth it. FWIW, I don't think we have any case where inheritance wouldn't work. For things like wl_callback that can never be bumped beyond version 1 it doesn't really matter if get_version() returns 5. It's still larger than 1.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>