<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - TearFree stops working at random with DRI3, works fine with DRI2" href="https://bugs.freedesktop.org/show_bug.cgi?id=109618#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - TearFree stops working at random with DRI3, works fine with DRI2" href="https://bugs.freedesktop.org/show_bug.cgi?id=109618">bug 109618</a> from <a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> Martin Peres</a> <pre>(In reply to Sultan Alsawaf from <a href="show_bug.cgi?id=109618#c15">comment #15</a>) > Hi Martin, > > This issue occurs immediately when I maximize a video in Chromium, and it > doesn't disappear until I restart X. Thanks for the information! > > I am indeed using DRI2 for the meantime, and I'm on the xf86-video-intel > driver because the modesetting driver wasn't so stable for me last I tried > it :-) Interesting, when was that? > > It's nice having tear-free graphics without the overhead of a composited > window manager; I've found even the "lightest" of composited window managers > to be more resource-heavy (and buggy!) than I'm willing to bear, so I am a > huge fan of the TearFree feature. I get your point. This is why I have invested some time to implement TearFree on modesetting (not done yet). However, for me, one of the most important advantage of not running with a compositor is the lower latency... but the tearfree feature goes against that. X11 is just not meant for provide a low-latency tear-free environment. Have you considered using sway by the way? This should be extremely light, tearfree and stable.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>