<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Application crashes after many hours of drawing" href="https://bugs.freedesktop.org/show_bug.cgi?id=71338#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Application crashes after many hours of drawing" href="https://bugs.freedesktop.org/show_bug.cgi?id=71338">bug 71338</a> from <a class="email" href="mailto:fourdan@xfce.org" title="Olivier Fourdan <fourdan@xfce.org>"> Olivier Fourdan</a> <pre>(In reply to jh4913895 from <a href="show_bug.cgi?id=71338#c19">comment #19</a>) > Our QA team ran into this issue recently. Upon further testing, the XNoOp > test still causes the IO error for a 32-bit program with libxcb 1.10-3 on > Debian 8 and libxcb 1.10-2 on Ubuntu 14.04 LTS. I don't see any mention of > a fix related to this issue in the libxcb 1.11 announcement. Because libxcb-1.11 predates the fix, see <a href="show_bug.cgi?id=71338#c18">comment #18</a> > Are there any plans to make a fix for this? The fix is made of 2 different patches for 2 different packages. 1. XCB needs to expose the 64bit sequence number by an API addition, this is <a href="show_bug.cgi?id=71338#c18">comment #18</a> 2. Xlib needs to make use of it, that's a separate (bigger) patch for libX11. But for #2 to happen, it requires an official release of libxcb that includes #1 (not 1.11) so that libX11 can depend on the appropriate XCB version that exposes the 64bit API.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>