Bug 187958

Summary: [GTK] Crash in WebCore::TextureMapperGC3DPlatformLayer::makeContextCurrent
Product: WebKit Reporter: Andres Gomez Garcia <agomez>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: bugs-noreply, cadubentzen, magomez, mcatanzaro, zan
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=201507
Attachments:
Description Flags
BT from gdb for the WebProcess none

Description Andres Gomez Garcia 2018-07-24 07:19:06 PDT 
Created attachment 345673 [details]
BT from gdb for the WebProcess

I'm using epiphany 3.29.3-63-ga1d6c75bf with WebKitGtk+ 2.21.5 from gnome-nightly's flatpak

When visiting https://asunnot.oikotie.fi/vuokrattavat-asunnot/helsinki/14691296 , the WebProcess SIGSEVs at WebCore::TextureMapperGC3DPlatformLayer::makeContextCurrent () at /run/build-runtime/WebKitGTK+/Source/WebCore/platform/graphics/texmap/TextureMapperGC3DPlatformLayer.cpp:61

I can reproduce 100%
Comment 1 Andres Gomez Garcia 2018-07-25 06:13:20 PDT 
Also, reproducible visiting:

https://www.magicleap.com/
Comment 2 Miguel Gomez 2018-07-31 07:34:15 PDT 
I cannot reproduce the crash with current ToT in either case. The crash probably means that there's GraphicsContext3D doesn't have a glContext, despite it should have been created with the GraphicsContext3D.

Andrés, I think you were running some version of mesa, can you see if reproducing the crash with MESA_DEBUG=1 gives some extra info?
Comment 3 Andres Gomez Garcia 2018-08-21 03:20:30 PDT 
I can still reproduce with epiphany 3.29.91-1-g8f26b7ff3 with WebKitGtk+ 2.21.5 from gnome-nightly's flatpak.

Now, I have tried to launch from the command line and I see these errors:

$ flatpak run org.gnome.Epiphany
Cannot get default EGL display: EGL_BAD_PARAMETER
WaylandCompositor requires eglCreateImage and eglDestroyImage.
Nested Wayland compositor could not initialize EGL

Can this be somehow related to bug 178896 ?


May it be a flatpak problem?


I do not know how to proceed from here :(
Comment 4 Michael Catanzaro 2020-03-19 18:53:19 PDT 
Looks very similar to bug #201507.
Comment 5 Michael Catanzaro 2020-10-11 10:53:59 PDT 
Probably a duplicate, absent evidence otherwise....

*** This bug has been marked as a duplicate of bug 201507 ***