[Webkit-unassigned] [Bug 199666] [GTK][X11] X Error received in WebProcess on NVidia binary drivers
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Oct 5 11:20:04 PDT 2020
https://bugs.webkit.org/show_bug.cgi?id=199666
Enrique Ocaña <eocanha at igalia.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eocanha at igalia.com
--- Comment #5 from Enrique Ocaña <eocanha at igalia.com> ---
(In reply to uwb17174 from comment #2)
> #0 0x00007f3b83929718 in
> WebCore::GLContextGLX::createPbufferContext(WebCore::PlatformDisplay&,
> __GLXcontextRec*)
> (platformDisplay=..., sharingContext=sharingContext at entry=0x0)
> at ../Source/WebCore/platform/graphics/glx/GLContextGLX.cpp:232
> fbConfigAttributes =
> {32784, 4, 32785, 1, 8, 1, 9, 1, 10, 1, 11, 1, 5, 0, 0}
> returnedElements = 56
> display = 0x55d0e47484c0
> configs = std::unique_ptr<__GLXFBConfigRec *> = {get() = 0x0}
> pbufferAttributes = {32833, 1, 32832, 1, 0}
> pbuffer = {m_resource = 1}
> context = std::unique_ptr<__GLXcontextRec> = {get() = 0x3100000007}
I'm also experiencing a crash in this very same place here, using NVidia proprietary drivers. I've reported it as bug 217323.
In both stacktraces, yours and mine, configs is pointing to null (so 0 elements have been returned by glXChooseFBConfig()) but returnedElements is different from zero. That's because glXChooseFBConfig() has an early return that leaves returnedElements untouched. It still holds its original uninitialized value, a random integer likely different from 0.
Once fixed the crash is gone, but I'm getting a different error, more similar to the one originally reported in this bug and out of the scope of bug 217323:
$ run-minibrowser --gtk http://google.com
libEGL warning: DRI2: failed to authenticate
(WebKitWebProcess:34): Gdk-WARNING **: 11:17:39.044: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was '179'.
(Details: serial 193 error_code 179 request_code 154 (unknown) minor_code 21)
(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.)
--
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/20201005/82abc73e/attachment-0001.htm>
More information about the webkit-unassigned
mailing list