[Webkit-unassigned] [Bug 277853] New: Stream IPC should have per-connection timeout and not per operation timeout

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=277853

            Bug ID: 277853
           Summary: Stream IPC should have per-connection timeout and not
                    per operation timeout
           Product: WebKit
           Version: WebKit Local Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit2
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: kkinnunen at apple.com
                CC: kkinnunen at apple.com
            Blocks: 277731

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.


Referenced Bugs:

https://bugs.webkit.org/show_bug.cgi?id=277731
[Bug 277731] GPU process is terminated during debugging
-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240809/113529da/attachment-0001.htm>