NEW181430
[GTK] WebProcess from WebKitGtk+ 2.19.3 SIGSEVs in WebKit::WebProcess::ensureNetworkProcessConnection() at Source/WebKit/WebProcess/WebProcess.cpp:1102 
https://bugs.webkit.org/show_bug.cgi?id=181430
Summary [GTK] WebProcess from WebKitGtk+ 2.19.3 SIGSEVs in WebKit::WebProcess::ensure...
Andres Gomez Garcia
Reported 2018-01-09 04:42:14 PST
Created attachment 330809 [details] BT from gdb for the WebProcess I'm using WebKitGtk+ with my own JHBuild setting: https://github.com/tanty/jhbuild-epiphany/tree/master Epiphany 3.24.1 and WebKit 2.19.3. The compilation was done with CMake args: '-DDEBUG_FISSION=OFF -DPORT=GTK -DCMAKE_BUILD_TYPE=Release -DENABLE_MINIBROWSER=ON -DUSE_WOFF2=OFF -DCMAKE_C_FLAGS_RELEASE="-O0 -g -DNDEBUG -DG_DISABLE_CAST_CHECKS -DRELEASE_WITHOUT_OPTIMIZATIONS" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g -DNDEBUG -DG_DISABLE_CAST_CHECKS -DRELEASE_WITHOUT_OPTIMIZATIONS"' After visiting several pages, eventually, the WebProcess hits a SIGSEV. This bug is not reproducible in a predictable way.
Attachments
BT from gdb for the WebProcess (334.57 KB, text/plain)
2018-01-09 04:42 PST, Andres Gomez Garcia 		no flags
Details
New bt (27.55 KB, text/plain)
2018-02-28 01:47 PST, Cédric Bellegarde 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Cédric Bellegarde
Comment 1 2018-02-28 01:46:17 PST
Can confirm the issue with 2.19.91
Cédric Bellegarde
Comment 2 2018-02-28 01:47:22 PST
Created attachment 334731 [details] New bt
Carlos Garcia Campos
Comment 3 2018-02-28 01:55:02 PST
This is probably a crash in the network process, so the interesting backtrace would be the network process one.
Andres Gomez Garcia
Comment 4 2018-02-28 02:28:58 PST
(In reply to Carlos Garcia Campos from comment #3) coredumpctl was not showing any core from the NetworkProcess when this happened.
Cédric Bellegarde
Comment 5 2018-02-28 02:29:34 PST
Can confirm, no core from NetworkProcess here in coredumpctl
Cédric Bellegarde
Comment 6 2018-02-28 02:35:50 PST
Seems to happen when closing a webpage/application.
Note You need to log in before you can comment on or make changes to this bug.