[Webkit-unassigned] [Bug 249145] [GTK] Regressions related to USE_ANGLE_WEBGL and WebGL 2 enablement

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=249145

--- Comment #4 from Carlos Garcia Campos <cgarcia at igalia.com> ---
I think we are assuming all the issues reported for 2.39 are due to angle, because some people are getting errors from angle when creating the EGL context. So, it's clear there's a problem there, but doesn't mean it's the source of all problems. The big changes between 2.38 and 2.39 are:

 - The ANGLE WebGL and WebGL2: it seems we are failing to create the GL context in some cases.

 - Async scrolling refactorings: I merged in 2.38 the commits actually fixing issues, but not all the other refactorings that shouldn't affect the behavior, but maybe there's a bug hidden there causing kinetic scrolling to fail for some people.

 - Threaded rendering disabled by default: this only affects GTK4 builds that used to have threaded rendering enabled. We detected some crashes and decided to disable it. This might be the cause of performance regressions, but it's easy to check because threaded rendering can still be enabled using the env var WEBKIT_NICOSIA_PAINTING_THREADS=4

 - Nested wayland compositor removed: I don't think this affects most of the users that should already be using the wpe renderer.

So, we would need to first find the cause of every regression before deciding to just disable angle or webgl. I know it's a pain, but bisecting is the best solution. I would do it myself if I could reproduce all the issues.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20221213/9849f87a/attachment.htm>