[TreesInViz] Send cc::Tile deletion updates to viz.

Currently when a Tile is destroyed in Renderer, the notification is not
sent to Viz and hence Viz does not delete its copy of those Tiles and
eventually runs out of tile memory limits.

This CL fixes that by calling
LayerTreeHostImpl::NotifyTileStateChanged() when a Tile is being
destroyed. Pending tree tile deletions are sent as a part of
|updated_tiles_| and active tree Tile deletions are sent immediately.

Note that when whole Tiling is deleted, it also deletes all the
corresponding Tiles which will result in
LayerTreeHostImpl::NotifyTileStateChanged(). If the Tiling deletion
happens on Pending Tree, none of the corresponding Tile deletions will
be send to Viz as there is no Tiling for those Tiles anymore in the
PictureLayerTilingSet. This is fine since future CLs will send Tiling
removal notifications to Viz and Viz can simply delete all the Tiles
corresponding to those Tilings.

If Tiling is deleted on active tree, all its corresponding Tile deletion
notifications will be send immediately to Viz irrespective of that
Tiling no longer present in PictureLayerTilingSet. When future CL send
Tiling removal notifications to viz, we should not send all its
corresponding Tile removal notifications.

Bug: 403385455
Change-Id: I5973ee49ce8e9d9e20b5c9dcd7d1105f2a7499e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6491732
Reviewed-by: Victor Miura <vmiura@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Auto-Submit: vikas soni <vikassoni@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1454591}
26 files changed
tree: 24cd0e3ac25ef9cd7dce8095a3658fc0177a7c25
  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.