
In the case of Speculative RenderFrameHosts deletion, we don't run any unload handlers. We remove the LifecycleStateImpl transition from kSpeculative -> kReadyToBeDeleted and the RenderFrameHost is deleted directly without doing any LifecycleState transitions for simplicity. BUG=1183639 Change-Id: I386f75f736cc425001a6b1386a370ed50a38edc3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3116418 Auto-Submit: Sreeja Kamishetty <sreejakshetty@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Alexander Timin <altimin@chromium.org> Commit-Queue: Sreeja Kamishetty <sreejakshetty@chromium.org> Cr-Commit-Position: refs/heads/main@{#918528}
14 lines
638 B
Plaintext
14 lines
638 B
Plaintext
// Generated with https://crrev.com/c/2220116 and:
|
|
// python3 tools/state_transitions/state_graph.py content/browser/renderer_host/render_frame_host_impl.cc LifecycleStateImpl
|
|
//
|
|
// See tools/state_transitions/README.md
|
|
digraph createflow {
|
|
kSpeculative -> {kActive, kPendingCommit};
|
|
kPendingCommit -> {kPrerendering, kActive, kReadyToBeDeleted};
|
|
kPrerendering -> {kActive, kRunningUnloadHandlers, kReadyToBeDeleted};
|
|
kActive -> {kInBackForwardCache, kRunningUnloadHandlers, kReadyToBeDeleted};
|
|
kInBackForwardCache -> {kActive, kReadyToBeDeleted};
|
|
kRunningUnloadHandlers -> {kReadyToBeDeleted};
|
|
kReadyToBeDeleted -> {};
|
|
}
|