<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - BadAccess errors in ShmAttach due to thread races with XNextRequest() usage in cairo-xlib-surface-shm.c" href="https://bugs.freedesktop.org/show_bug.cgi?id=98883#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - BadAccess errors in ShmAttach due to thread races with XNextRequest() usage in cairo-xlib-surface-shm.c" href="https://bugs.freedesktop.org/show_bug.cgi?id=98883">bug 98883</a> from <a class="email" href="mailto:bugs.freedesktop@karlt.net" title="Karl Tomlinson <bugs.freedesktop@karlt.net>"> Karl Tomlinson</a> <pre>(In reply to Daniel van Vugt from <a href="show_bug.cgi?id=98883#c11">comment #11</a>) > <a href="attachment.cgi?id=139297" name="attach_139297" title="Handle-XShmAttach-failures-v1.patch">attachment 139297</a> <a href="attachment.cgi?id=139297&action=edit" title="Handle-XShmAttach-failures-v1.patch">[details]</a> <a href='page.cgi?id=splinter.html&bug=98883&attachment=139297'>[review]</a> [review] mentions multiple times "why" it is > necessary to make it synchronous. Because it's impossible to detect errors > in XShmAttach otherwise. It is not impossible to detect errors without XSync. Display::async_handlers can be used. The result would be async and the patch comment claims that _cairo_xlib_shm_pool_create must return a reliable status synchronously. I haven't check that claim, but if so, I wonder whether it would be possible to take a fallback path until the pool is successfully created.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>