<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [Regression, bisected] Tooltip corruption in Chrome" href="https://bugs.freedesktop.org/show_bug.cgi?id=90264#c44">Comment # 44</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [Regression, bisected] Tooltip corruption in Chrome" href="https://bugs.freedesktop.org/show_bug.cgi?id=90264">bug 90264</a> from <a class="email" href="mailto:lil_tux@web.de" title="Heiko <lil_tux@web.de>"> Heiko</a> <pre>(In reply to Antoine Labour from <a href="show_bug.cgi?id=90264#c43">comment #43</a>) > I see, the XResizeWindow would cause a DRI2 Invalidate event on the server > side, and the XSync would make sure it's handled on the client before > anything else happens. That seems like it would do the right thing (at the > cost of a server round-trip). Well, from what I figured, chromium gets about 2-5 XExpose events per tooltip resizing after the XMapWindow call. As per XMapWindow manpage, the tooltip window seems to get tiled into the original region plus horizontal extension, plus vertical extension. Though, sometimes, there's additional XExpose for another horizontal extension of the tooltip. Thus you get 2-5 Calls into ::ScheduleRedrawRect and probably also 2-5 calls to glViewport (I bet that's the reason for the 'weird' values I found in apitrace). Also there are some XExpose events with send_event true. Would it be possible to build a single (damage_)rect (for a time slice) to get most or all parts of the tooltip into one draw call? For the generic case: I thought one would need the round-trip to the server to make sure X and GL are in sync. Or what would be some other way; short sleep, some GL-Redraw? Not sure how the binary blobs handle this, but I bet they also call XSync/XFlush.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>