Google Git
Sign in
chromium / chromium / src / 0c028c6ff61a8121afbce47157bef21a6cf7e6fb
commit0c028c6ff61a8121afbce47157bef21a6cf7e6fb[log] [tgz]
authorLingqi Chi <lingqi@chromium.org>Wed Jul 19 03:05:19 2023
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 19 03:05:19 2023
treebeeb200e62cc6be29c8cd9d9c0fcefb26999bf84
parent7036c83397c899a63c8c84445e934bfbe04678b0 [diff]
Reland "Prerender: Record activation IPC delay"

This is a reland of commit 254d9b73fef39806bf919e4fc309e3dc63c24e0b
Due to an existing bug(1415185), NavigatePrimaryPage cannot really wait for the prerendering page to finish loading, and cannot tell
whether the activation signal has been sent to the renderer side or not.

This reland makes the test code send another signal to the renderer
side explicitly, to ensure all signals have been processed, as a
workaround

Original change's description:
> Prerender: Record activation IPC delay
>
> It is possible that the activation IPC was queueing for quite a long
> time before being processed.
> This CL adds a metric to track the delay
>
> Bug: 1462834, 1342497
> Change-Id: I196f5d22b9089d9d1b9ca9b2ff45b9367849013a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4671290
> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
> Commit-Queue: Lingqi Chi <lingqi@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1170412}

Bug: 1462834, 1342497
Change-Id: Ic590fb7b82408c7ede9ccd08ef2f6c762b03a3bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4692484
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Lingqi Chi <lingqi@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1172142}
4 files changed
tree: beeb200e62cc6be29c8cd9d9c0fcefb26999bf84
  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. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  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.