Read BrowserPeriodicYieldingToNative params after FeatureList initialization.

The FeatureList is initialized after the construction of the
BrowserUIThreadScheduler and MessagePumpForUI:

  BrowserUIThreadScheduler: https://source.chromium.org/chromium/chromium/src/+/main:content/app/content_main_runner_impl.cc;l=1154;drc=e60bbf14121cbc814325dd222fec20d6a7a2a54c
    BrowserUIThreadScheduler::BrowserUIThreadScheduler
    BrowserTaskExecutor::Create

  MessagePumpForUI: https://source.chromium.org/chromium/chromium/src/+/main:content/app/content_main_runner_impl.cc;l=1154;drc=e60bbf14121cbc814325dd222fec20d6a7a2a54c
    MessagePumpForUI::MessagePumpForUI
    base::MessagePump::Create
    BrowserUIThreadScheduler::BrowserUIThreadScheduler
    BrowserTaskExecutor::Create

  FeatureList: https://source.chromium.org/chromium/chromium/src/+/main:content/app/content_main_runner_impl.cc;l=1163;drc=e60bbf14121cbc814325dd222fec20d6a7a2a54c
    FeatureList::SetInstance
    VariationsService::SetUpFieldTrials
    ChromeFeatureListCreator::SetUpFieldTrials
    ChromeFeatureListCreator::CreateFeatureList
    ChromeMainDelegate::PostEarlyInitialization

As a result, BrowserUIThreadScheduler and MessagePumpForUI currently
get the default values of the BrowserPeriodicYieldingToNative params,
instead of those overridden by the variations service or the command
line. This CL makes BrowserUIThreadScheduler and MessagePumpForUI
read the params after FeatureList initialization, so they get the
correct overridden values and to unblock this CL
https://crrev.com/c/3867967 which adds a DCHECK to prevent this
problem from happening again in the future.

(cherry picked from commit 253a306132ecfde6df9fc2cafe3cbada9191a118)

Bug: 1358639, 1215076
Change-Id: Ice12da8d42d68274db150887088dc7928ff2d6b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3949402
Reviewed-by: Stephen Nusko <nuskos@chromium.org>
Auto-Submit: Francois Pierre Doray <fdoray@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Francois Pierre Doray <fdoray@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1062857}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3984705
Reviewed-by: Francois Pierre Doray <fdoray@chromium.org>
Commit-Queue: Omar Elmekkawy <mekk@chromium.org>
Cr-Commit-Position: refs/branch-heads/5359@{#334}
Cr-Branched-From: 27d3765d341b09369006d030f83f582a29eb57ae-refs/heads/main@{#1058933}
4 files changed
tree: 1eb1fa2e1496bbfc33de9b2e2f2bca948e112817
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.