Introduce ProcessRankPolicyAndroid

ProcessRankPolicyAndroid introduces the memory process priority concept
to Chrome on Android. This is to unblock introducing protected tab
concept to Chrome on Android which requires Performance Manager (e.g.
user edit information is only stored in PageNode out of Blink).

ProcessRankPolicyAndroid replaces TabImportanceManager.java which has
updated content::ChildProcessImportance via
WebContentsAndroid::SetImportance() which calls
RenderWidgetHostImpl::SetImportance().

ProcessRankPolicyAndroid contains the whole logic of
TabImportanceManager.java and visibility related conditions for main
frame in ChildProcessLauncherHelperImpl.setPriority().

* From TabImportanceManager:
  * Boosts the importance of the main frame of the focused tab to
    ChildProcessImportance::IMPORTANT with ChangeUnfocusedPriority.
  * Boosts the importance of the main frame of active tabs in invisible
    windows to ChildProcessImportance::MODERATE.
* From ChildProcessLauncherHelperImpl.setPriority():
  * Boosts the importance of the main frame of non-focused but visible
    tabs to ChildProcessImportance::IMPORTANT (if
    ChangeUnfocusedPriority is disabled) or
    ChildProcessImportance::MODERATE (if ChangeUnfocusedPriority is
    enabled)

ProcessRankPolicyAndroid does nothing to do with other frames in a page
other than the main frame. The priority of sub-frame processes are
updated by the existing logic in
ChildProcessLauncherHelperImpl.setPriority() which boosts sub-frames
with media stream and intersecting visible sub-frames.

Memory priority for sub-frames from Performance Manager will be done
later.

This also renames setImportance() method of WebContents.java
setPrimaryMainFrameImportance(). Historically the method had updated all
sub-frame importance, and https://crrev.com/c/1038759 changed it to
update the main frame only without renaming the java API.

DesignDocument: go/clank-memory-priority-policy

Bug: 401498479
Change-Id: I9046295757ed04a706ff9b9fe34f8b4f846ec81d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6335184
Reviewed-by: Bo Liu <boliu@chromium.org>
Reviewed-by: Patrick Monette <pmonette@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Shin Kawamura <kawasin@google.com>
Cr-Commit-Position: refs/heads/main@{#1445059}
21 files changed
tree: fd5c204018c25e28aabfc9cc368d38d6f5af4e73
  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.