Bug 277853
| Summary: | Stream IPC should have per-connection timeout and not per operation timeout | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Kimmo Kinnunen <kkinnunen> |
| Component: | WebKit2 | Assignee: | Kimmo Kinnunen <kkinnunen> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | kkinnunen, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Local Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=278086 | ||
| Bug Depends on: | |||
| Bug Blocks: | 277731 | ||
Kimmo Kinnunen
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
<rdar://problem/133534897>
Kimmo Kinnunen
Pull request: https://github.com/WebKit/WebKit/pull/31945
EWS
Committed 282161@main (ba7276757824): <https://commits.webkit.org/282161@main>
Reviewed commits have been landed. Closing PR #31945 and removing active labels.