(In reply to Eero Tamminen from comment #1)
> Does Mesa commit f7a355556ef5fe23056299a77414f9ad8b5e5a1d help?
I'll try to test this as soon as I can. Sorry for the delay.
> (It works around DRI3 sync slowdown, but there are also other slowdown bugs
> for DRI3 here in FDO bugtracker, just search for "DRI3".)
>
> Does Epiphany/WebKitGTK+ uses GL for something else besides WebGL
Yes, most notably for accelerated compositing:
"alex: I mean, accelerated compositing is activated by default and probably is creating some graphic layers that are composited using GL in that webpage"
> , or do
> these problematic pages use WebGL?
We actually have WebGL disabled by default.
> Or how Mesa is involved in this (DRI3 is
> mainly X server side thing)?
It might not be a mesa bug; I just filed against mesa because bug #81623 was filed against mesa.
(In reply to Eero Tamminen from comment #1) 3056299a77414f9 ad8b5e5a1d help?
> Does Mesa commit f7a355556ef5fe2
I'll try to test this as soon as I can. Sorry for the delay.
> (It works around DRI3 sync slowdown, but there are also other slowdown bugs
> for DRI3 here in FDO bugtracker, just search for "DRI3".)
>
> Does Epiphany/WebKitGTK+ uses GL for something else besides WebGL
Yes, most notably for accelerated compositing:
"alex: I mean, accelerated compositing is activated by default and probably is creating some graphic layers that are composited using GL in that webpage"
> , or do
> these problematic pages use WebGL?
We actually have WebGL disabled by default.
> Or how Mesa is involved in this (DRI3 is
> mainly X server side thing)?
It might not be a mesa bug; I just filed against mesa because bug #81623 was filed against mesa.