Annotate locks in PipelineImpl::RendererWrapper

The "WebMediaPlayer_MainThread" MemoryDumpProvider can take a long time
to run. I suspect the cause is contention on the lock for
RendererWrapper::SharedState, which is taken by GetPipelineStatistics()
during a memory dump.

The lock semantics are complicated. To help in the investigation, this
adds SEQUENCE_CHECKER and EXCLUDED_LOCKS_REQUIRED annotations to make
sure the locks are being accessed as described in the SharedState
documentation comment. SharedState is now owned by a wrapper class,
SharedStateAccessor, that exposes const refs to SharedState on all
threads, but only exposes a mutable ref to the media thread.

This uncovered two existing issues:

 * `did_loading_progress` is written from both threads, contradicting the documented semantics. To support this, it's moved to SharedStateAccessor with its own EXCLUSIVE_LOCKS_REQUIRED annotation.
 * ReportMetadata() writes `suspend_timestamp` without holding the lock. Added the missing lock.

Also removed a lock in RenderWrapper::Resume that was shown to be
unneeded.

Bug: 41419817,450929521
Change-Id: Iefd4c47b8080bf53e808769747601136fab755be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7506130
Commit-Queue: Joe Mason <joenotcharles@google.com>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1573465}
1 file changed
tree: 5365e27d0e1b0174d05abfd3ca7b61915bfbbd2c
  1. .claude/
  2. .gemini/
  3. .github/
  4. agents/
  5. android_webview/
  6. apps/
  7. ash/
  8. base/
  9. build/
  10. build_overrides/
  11. buildtools/
  12. cc/
  13. chrome/
  14. chromecast/
  15. chromeos/
  16. codelabs/
  17. components/
  18. content/
  19. crypto/
  20. dbus/
  21. device/
  22. docs/
  23. extensions/
  24. fuchsia_web/
  25. gin/
  26. google_apis/
  27. gpu/
  28. headless/
  29. infra/
  30. ios/
  31. ipc/
  32. media/
  33. mojo/
  34. net/
  35. pdf/
  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. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .cursorignore
  55. .geminiignore
  56. .git-blame-ignore-revs
  57. .gitallowed
  58. .gitattributes
  59. .gitignore
  60. .gitmodules
  61. .gn
  62. .mailmap
  63. .rustfmt.toml
  64. .vpython3
  65. .yapfignore
  66. ATL_OWNERS
  67. AUTHORS
  68. BUILD.gn
  69. CODE_OF_CONDUCT.md
  70. codereview.settings
  71. CPPLINT.cfg
  72. CRYPTO_OWNERS
  73. DEPS
  74. DIR_METADATA
  75. LICENSE
  76. LICENSE.chromium_os
  77. OWNERS
  78. package.json
  79. PRESUBMIT.py
  80. PRESUBMIT_test.py
  81. PRESUBMIT_test_mocks.py
  82. README.md
  83. SECURITY_OWNERS
  84. 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.