[webkit-changes] [WebKit/WebKit] ee5c4b: waitForDidUpdateActivityState can block for 250ms ...

mattwoodrow noreply at github.com
Wed Oct 18 13:56:53 PDT 2023


  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: ee5c4b70a09cc5c2050d08b3bf0005c06b3cf3db
      https://github.com/WebKit/WebKit/commit/ee5c4b70a09cc5c2050d08b3bf0005c06b3cf3db
  Author: Matt Woodrow <mattwoodrow at apple.com>
  Date:   2023-10-18 (Wed, 18 Oct 2023)

  Changed paths:
    M Source/WebKit/UIProcess/RemoteLayerTree/RemoteLayerTreeDrawingAreaProxy.mm

  Log Message:
  -----------
  waitForDidUpdateActivityState can block for 250ms waiting for a message that isn't pending.
https://bugs.webkit.org/show_bug.cgi?id=263275
<rdar://113318934>

Reviewed by Simon Fraser.

RemoteLayerTreeDrawingAreaProxy::waitForDidUpdateActivityState sends a didRefreshDisplay message
to the web content process (if one was pending) to ensure that the web process knows it can commit
a new layer tree.

If the incoming CommitLayerTree message didn't include the right activity state change, then we
wait again, but don't send a new didRefreshDisplay, and we wait for a message that isn't coming.

* Source/WebKit/UIProcess/RemoteLayerTree/RemoteLayerTreeDrawingAreaProxy.mm:
(WebKit::RemoteLayerTreeDrawingAreaProxy::waitForDidUpdateActivityState):

Canonical link: https://commits.webkit.org/269486@main




More information about the webkit-changes mailing list