[Webkit-unassigned] [Bug 189179] New: GLContextGLX::createWindowContext should cope when no config is found

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Aug 30 20:15:40 PDT 2018


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

            Bug ID: 189179
           Summary: GLContextGLX::createWindowContext should cope when no
                    config is found
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: drake at endlessm.com
                CC: bugs-noreply at webkitgtk.org

We are seeing a crash on Intel GeminiLake platforms where the web process crashes with:

(WebKitWebProcess:5058): Gdk-ERROR **: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadFBConfig'.
  (Details: serial 202 error_code 178 request_code 155 (GLX) minor_code 34)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Tracing through, this happens because WebKit is calling glXCreateContextAttribsARB() with a NULL GLXFBConfig. This causes glvnd to raise an X error.

Why was GLContextGLX::createWindowContext unable to find a usable FBConfig? I don't fully understand the situation; I've provided some detail on it here:
https://lists.freedesktop.org/archives/xorg-devel/2018-August/057477.html

Regardless of that, it seems like webkit should probably do something better than it currently does (crash) when no config is found, e.g. fall back on non-composited gfx codepath?

-- 
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/20180831/e4156177/attachment.html>


More information about the webkit-unassigned mailing list