[Webkit-unassigned] [Bug 210269] [GTK] segfault creating GL context in VNC

[bugzilla-daemon at webkit.org]

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

--- Comment #3 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---
(In reply to Thomas Klausner from comment #2)
> Thank you for the links.
> 
> The workaround you provide with setting WEBKIT_DISABLE_COMPOSITING_MODE=1
> indeed avoids the coredump for me. Thank you!
> 
> However, this leaves me with more questions :)
> 
> Getting core dumps is not nice for users, and the setting is not easily
> guessable. So I assume applications should check more carefully before
> calling webkit-gtk, or set it up differently. Is there something I can tell
> the foliate developers to do to avoid the crash?
> 

Honestly, this its's kind of a corner-case. As of 2020 everyone running a Desktop should have some way of running OpenGL content.

Even in your example (VNC) you can have OpenGL on it. Maybe that its not easy on NetBSD (no idea), but at least on GNU/Linux its easy to do thanks to Xvfb/Mesa/llvmpipe.

BTW, also note that WebKitGTK has an option to disable OpenGL at build-time. If you do that you not longer need to disable it at run-time (it will always default to disable the hardware-acceleration codepaths).


> As an example for a positive experience with webkit-gtk in the same
> environment: I have been using gnucash for many years, and gnucash embeds a
> HTML viewer using webkit-gtk. I have never had a crash in gnucash because of
> this problem.

Well, I was wrong before when I said that WebKitGTK defaults to enable hardware-acceleration. In reality it just defaults to set it as "on-demand". That means that it will not trigger the hardware-acceleration paths until some web-content requires it (like for example some Web content trying to use CSS 3D transforms).

So I suspect that GNUCash works without trouble for you because the Web content rendered by GNUCash its simple enough that it doesn't trigger any hadware-acelerated codepaths in WebKitGTK.

But, on your other example (foliate) some web-content its liekly triggering this codepath, and that causes a crash when WebKitGTK tries to enter into the hardware-accelerated mode to better render this content (but your system doesn't allow it to call into OpenGL).

-- 
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/20200410/dc8fb745/attachment.htm>