Bug 2065464

Summary: [abrt] webkit2gtk3: WebKit::getNetworkProcessConnection(): WebKitWebProcess killed by SIGABRT
Product: [Fedora] Fedora Reporter: Rory Mobley <rorymobley5>
Component: webkit2gtk3Assignee: Michael Catanzaro <mcatanza>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: bugzilla-redhat-3187, erack, m.cami, mcatanza, nixuser, pradeepk.dev, tpopela
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8326fe826cbeb9d58887794b16f596460d5f1c7e
Whiteboard: abrt_hash:7b007c482ac3508e6e5425bed4071449123dfccd;VARIANT_ID=workstation;
Fixed In Version: webkit2gtk3-2.36.1-1.fc35 webkit2gtk3-2.36.1-1.fc36 webkit2gtk3-2.36.1-1.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-24 20:06:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Rory Mobley 2022-03-17 22:10:23 UTC 
Version-Release number of selected component:
webkit2gtk3-2.35.90-1.fc36

Additional info:
reporter:       libreport-2.17.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-glib-xreader-171170.scope
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 12 23
crash_function: WebKit::getNetworkProcessConnection
executable:     /usr/libexec/webkit2gtk-4.0/WebKitWebProcess
journald_cursor: s=970cfe5ae71141c7a0152d3bf57cfc6b;i=dedba;b=640a9effc18f4662ba4867c3bd9b24d5;m=4bd87db42;t=5da7106016453;x=f3fe41c9f779c28a
kernel:         5.17.0-0.rc7.116.fc36.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #4 WebKit::getNetworkProcessConnection at /usr/src/debug/webkit2gtk3-2.35.90-1.fc36.x86_64/Source/WebKit/WebProcess/WebProcess.cpp:1137
 #5 WebKit::WebProcess::ensureNetworkProcessConnection at /usr/src/debug/webkit2gtk3-2.35.90-1.fc36.x86_64/Source/WebKit/WebProcess/WebProcess.cpp:1155
 #6 WebKit::WebProcess::initializeWebProcess at /usr/src/debug/webkit2gtk3-2.35.90-1.fc36.x86_64/Source/WebKit/WebProcess/WebProcess.cpp:404
 #7 IPC::callMemberFunctionImpl<WebKit::WebProcess, void (WebKit::WebProcess::*)(WebKit::WebProcessCreationParameters&&), std::tuple<WebKit::WebProcessCreationParameters>, 0ul> at /usr/src/debug/webkit2gtk3-2.35.90-1.fc36.x86_64/Source/WebKit/Platform/IPC/HandleMessage.h:125
 #8 IPC::callMemberFunction<WebKit::WebProcess, void (WebKit::WebProcess::*)(WebKit::WebProcessCreationParameters&&), std::tuple<WebKit::WebProcessCreationParameters>, std::integer_sequence<unsigned long, 0ul> > at /usr/src/debug/webkit2gtk3-2.35.90-1.fc36.x86_64/Source/WebKit/Platform/IPC/HandleMessage.h:131
Comment 1 Rory Mobley 2022-03-17 22:10:26 UTC 
Created attachment 1866514 [details]
File: backtrace
Comment 2 Rory Mobley 2022-03-17 22:10:27 UTC 
Created attachment 1866515 [details]
File: core_backtrace
Comment 3 Rory Mobley 2022-03-17 22:10:28 UTC 
Created attachment 1866516 [details]
File: cpuinfo
Comment 4 Rory Mobley 2022-03-17 22:10:29 UTC 
Created attachment 1866517 [details]
File: dso_list
Comment 5 Rory Mobley 2022-03-17 22:10:30 UTC 
Created attachment 1866518 [details]
File: environ
Comment 6 Rory Mobley 2022-03-17 22:10:31 UTC 
Created attachment 1866519 [details]
File: limits
Comment 7 Rory Mobley 2022-03-17 22:10:32 UTC 
Created attachment 1866520 [details]
File: maps
Comment 8 Rory Mobley 2022-03-17 22:10:32 UTC 
Created attachment 1866521 [details]
File: mountinfo
Comment 9 Rory Mobley 2022-03-17 22:10:33 UTC 
Created attachment 1866522 [details]
File: open_fds
Comment 10 Rory Mobley 2022-03-17 22:10:34 UTC 
Created attachment 1866523 [details]
File: proc_pid_status
Comment 11 Michael Catanzaro 2022-03-18 14:53:05 UTC 
Hm, looks like it crashes if it takes more than one second to connect to the network process. That's a *really* long timeout, but seems like it could happen if your computer is thrashing extremely badly?

I think a crash is probably the right thing to do in this case. It's either that, or exit with a fail status, but that's probably worse because it leaves no backtrace and will leave us no way to know what has gone wrong. So probably the only thing to consider changing here would be the timeout, but even then, one second is quite a lot.
Comment 12 Michael Catanzaro 2022-03-22 18:22:17 UTC 
After upgrading to F36, I hit this twice so far today when using Geary. I wonder what has changed.

I kinda suspect Geary might be at fault, though, because it experiences frequent long UI process freezes, which could easily trip this 1 second timeout check.
Comment 13 Michael Catanzaro 2022-03-24 14:46:49 UTC 
I just hit this twice with Epiphany too. Sadly it's been two years since anything changed in WebProcess::ensureNetworkProcessConnection.

I will forward this to upstream.
Comment 14 Michael Catanzaro 2022-03-28 19:14:42 UTC 
*** Bug 2069339 has been marked as a duplicate of this bug. ***
Comment 15 Michael Catanzaro 2022-03-30 01:07:44 UTC 
*** Bug 2069883 has been marked as a duplicate of this bug. ***
Comment 16 Michael Catanzaro 2022-04-20 18:55:03 UTC 
*** Bug 2077091 has been marked as a duplicate of this bug. ***
Comment 17 Fedora Update System 2022-04-22 01:13:09 UTC 
FEDORA-2022-462e524445 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-462e524445
Comment 18 Fedora Update System 2022-04-22 01:13:11 UTC 
FEDORA-2022-86a5792181 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-86a5792181
Comment 19 Fedora Update System 2022-04-22 01:13:13 UTC 
FEDORA-2022-ea3cf12f91 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ea3cf12f91
Comment 20 Fedora Update System 2022-04-22 05:59:47 UTC 
FEDORA-2022-462e524445 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-462e524445`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-462e524445

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 21 Fedora Update System 2022-04-22 06:59:25 UTC 
FEDORA-2022-86a5792181 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-86a5792181`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-86a5792181

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 22 Fedora Update System 2022-04-22 07:15:04 UTC 
FEDORA-2022-ea3cf12f91 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-ea3cf12f91`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ea3cf12f91

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 23 Fedora Update System 2022-04-24 20:06:14 UTC 
FEDORA-2022-ea3cf12f91 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 24 Michael Catanzaro 2022-04-24 21:51:18 UTC 
*** Bug 2078152 has been marked as a duplicate of this bug. ***
Comment 25 Fedora Update System 2022-05-07 04:29:06 UTC 
FEDORA-2022-462e524445 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 26 Fedora Update System 2022-05-08 02:01:33 UTC 
FEDORA-2022-86a5792181 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 27 Steven Schlansker 2022-08-04 21:27:18 UTC 
Similar problem has been detected:

Using Eclipse's embedded WebKit renderer

reporter:       libreport-2.17.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 265 88
crash_function: WebKit::getNetworkProcessConnection
executable:     /usr/libexec/webkit2gtk-4.0/WebKitWebProcess
journald_cursor: s=930166a8fc5142869663ca5c45a86182;i=6f5896;b=92f6eb9550474496a4cfedbc5481f394;m=424ec1e1e;t=5e570301d9ad8;x=ca93051b745d4e2f
kernel:         5.18.13-200.fc36.x86_64
package:        webkit2gtk3-2.36.0-1.fc36
reason:         WebKitWebProcess killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000