RESOLVED FIXED 277853
Stream IPC should have per-connection timeout and not per operation timeout 
https://bugs.webkit.org/show_bug.cgi?id=277853
Summary Stream IPC should have per-connection timeout and not per operation timeout
Kimmo Kinnunen
Reported 2024-08-09 05:34:36 PDT
Stream IPC should have per-connection timeout and not per operation timeout There is no distinct logic that can be applied per different message sent. If the receiver hangs so that send times out, it does not matter which message it is -- there cannot be a different timeout to A and B. Same logic applies for waits vs sends. There are no useful waits that can be let timing out. If a wait timeout happens, the receiver must be assumed to be hung.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2024-08-09 05:36:12 PDT
<rdar://problem/133534897>
Kimmo Kinnunen
Comment 2 2024-08-09 05:55:08 PDT
Pull request: https://github.com/WebKit/WebKit/pull/31945
EWS
Comment 3 2024-08-13 03:31:53 PDT
Committed 282161@main (ba7276757824): <https://commits.webkit.org/282161@main> Reviewed commits have been landed. Closing PR #31945 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.