238325 2022-03-24 07:54:35 -0700 REGRESSION(r??????): [GTK] Web process crash in WebKit::getNetworkProcessConnection 2022-03-24 08:50:00 -0700 1 1 1 Unclassified WebKit WebKitGTK WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 235224 https://bugzilla.redhat.com/show_bug.cgi?id=2065464 P2 Normal --- 1 mcatanzaro webkit-unassigned bugs-noreply cgarcia oldest_to_newest 1854675 0 mcatanzaro 2022-03-24 07:54:35 -0700 Since upgrading from F35 -> F36 and 2.34.x -> 2.36.0, I've seen Geary's web process crash several times when the netwokr process takes more than one second to start. I've also seen this twice today in Epiphany after upgrading Tech Preview from GTK 3 -> GTK 4. I'm not the only one. The backtrace looks like this: (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #1 0x00007fee64511867 in __GI_abort () at abort.c:79 #2 0x00007fee64d6f89b in WebKit::getNetworkProcessConnection (connection=<optimized out>) at /usr/lib/debug/source/sdk/webkit2gtk-5.0.bst/Source/WebKit/WebProcess/WebProcess.cpp:1135 #3 WebKit::WebProcess::ensureNetworkProcessConnection() (this=0x7fee56af3000) at /usr/lib/debug/source/sdk/webkit2gtk-5.0.bst/Source/WebKit/WebProcess/WebProcess.cpp:1153 #4 0x00007fee653759cc in WebKit::WebProcess::initializeWebProcess(WebKit::WebProcessCreationParameters&&) (this=0x7fee56af3000, parameters=...) at /usr/lib/debug/source/sdk/webkit2gtk-5.0.bst/Source/WebKit/WebProcess/WebProcess.cpp:404 #5 0x00007fee64ec3f6f in IPC::callMemberFunctionImpl<WebKit::WebProcess, void (WebKit::WebProcess::*)(WebKit::WebProcessCreationParameters&&), std::tuple<WebKit::WebProcessCreationParameters>, 0ul>(WebKit::WebProcess*, void (WebKit::WebProcess::*)(WebKit::WebProcessCreationParameters&&), std::tuple<WebKit::WebProcessCreationParameters>&&, std::integer_sequence<unsigned long, 0ul>) (args=..., function=<optimized out>, object=0x7fee56af3000) at /usr/include/c++/11.2.0/tuple:219 Sadly, it looks like there are no recent changes to WebProcess::ensureNetworkProcessConnection, so I'm not sure what changed. Maybe we somehow made the network process slower? 1854694 1 cgarcia 2022-03-24 08:50:00 -0700 *** This bug has been marked as a duplicate of bug 235224 ***