[PM] Fix consistency in OnBeforeFooRemoved notifications

Makes sure that when OnBeforeFooRemoved() is called, all connections
to other graph nodes are still intact. This makes
OnBeforeFooRemoved() the last chance to iterate the graph with the
old connections.

As an exception, when a connection has its own notification (such as
OnOpenerFrameNodeChanged() for the PageNode<->FrameNode "opener"
connection) it can be broken before OnBeforeFooRemoved() if all
observers are notified. From the observer's point of view this is
indistinguishable from a separate event that happens to break the
connection shortly before the node is removed, so the graph is still
consistent during each notification.

To implement the new semantic, this splits the internal NodeBase::OnBeforeLeavingGraph() into 2 stages:

* OnBeforeLeavingGraph() lets the node make changes that don't affect
  the graph topology. It's called before sending OnBeforeFooRemoved
  notifications.
* OnUninitializing() lets the node finish its cleanup and break
  connections to other nodes. It's called after sending
  OnBeforeFooRemoved notifications.

Also updates the only two node observers that are affected by this
change:

* FreezingPolicy::OnBeforeFrameNodeRemoved() had several hidden
  assumptions that the FrameNode was NOT reachable from its PageNode.
  Now that it is reachable, it must be explicitly excluded.
* CPUMeasurementMonitor::OnBeforeFrameNodeRemoved() has a requirement
  that the FrameNode IS reachable from its PageNode. Now that this is
  true, removed the GraphChangeRemoveFrame workaround.
  OnBeforeWorkerNodeRemoved() has similar changes.

R=pmonette

Bug: 40640034
Change-Id: I0164da136ce085332f3e1b19ef125fc83ab2202c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5476608
Reviewed-by: Patrick Monette <pmonette@chromium.org>
Commit-Queue: Joe Mason <joenotcharles@google.com>
Cr-Commit-Position: refs/heads/main@{#1392613}
15 files changed
tree: ec121e04f3d2f15f9e015eccc6233bd2b490c98a
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.