[Webkit-unassigned] [Bug 232580] [GPU Process] Rendering backend may stop processing IPC stream messages after a sync message timeout

[bugzilla-daemon at webkit.org]

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

--- Comment #2 from Kimmo Kinnunen <kkinnunen at apple.com> ---
Yeah.
The design is so that timeouts do not make sense.

If WP asks to draw a 4k x 4k image, and that never completes, there's nothing sensible you can do except restart the GPU process.

The rationale:
We define timeout as X seconds, e.g. if message is not replied within X seconds, we declare the GPU process has hung.

You send message.
The message times out.
What do you do now?

A) Maybe GPUP has not hung, we should be able to retry something like 3 times
  - If the GPUP has not hung, why did you define "GPUP is hung if timeout X seconds"?
  - I still want to retry 3 times
  - Why did you not define "GPUP is hung if timeout is 3*X seconds"? What does the 
    retry contribute here?
  - ...

B) We did define X sec timeout means GPU process has hung, so GPU process has hung. Restart it.


"Retry" or "carry on like nothing happened and hope for the best" is ok if the medium is such that it's expected that messages get lost, like a network. IPC isn't like that, nothing should be lost by design.

-- 
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/20211102/378495b5/attachment.htm>