Fredrik Höglund writes:
> On Tuesday 07 May 2013, Eric Anholt wrote:
>> Ever since fake front was introduced in
>> 63b51b5cf17ddde09b72a2811296f37b9a4c5ad2, we were skipping the XSync() in
>> the non-fake-front path, so compositors like Firefox's GL canvas were
>> having to manually put it in out
On Tuesday 07 May 2013, Eric Anholt wrote:
> Ever since fake front was introduced in
> 63b51b5cf17ddde09b72a2811296f37b9a4c5ad2, we were skipping the XSync() in
> the non-fake-front path, so compositors like Firefox's GL canvas were
> having to manually put it in outside of glXWaitX().
>
> Bugzill
On 05/06/2013 05:39 PM, Eric Anholt wrote:
Ever since fake front was introduced in
63b51b5cf17ddde09b72a2811296f37b9a4c5ad2, we were skipping the XSync() in
the non-fake-front path, so compositors like Firefox's GL canvas were
having to manually put it in outside of glXWaitX().
Bugzilla: https:/
Ever since fake front was introduced in
63b51b5cf17ddde09b72a2811296f37b9a4c5ad2, we were skipping the XSync() in
the non-fake-front path, so compositors like Firefox's GL canvas were
having to manually put it in outside of glXWaitX().
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=52930
-