media: Add patterned DroppedFrameCount2/FrameReadBackCount UMAs

This CL adds patterned UMAs to monitor DroppedFrameCount2 and
FrameReadBackCount based on RendererType for video playbacks, e.g. the
MediaFoundationRenderer from MF Frame Server Mode Clear video playbacks.
For DroppedFrameCount2, it is also patterned with Clear/Encrypted.
FrameReadBackCount only applies to Clear video playback.

UMAs added:
- Media.DroppedFrameCount2.{RendererType}.{ClearOrEncrypted}
- Media.FrameReadBackCount.{RendererType}

Manually tested by exercising canvas/video playbacks with/without
enabling of `chrome://flags/#enable-media-foundation-clear`. The
followings are reported/verified in about://histograms:
```
// chrome://flags/#enable-media-foundation-clear enabled:
- Histogram: Media.DroppedFrameCount2.MediaFoundationRenderer.Clear recorded 1 samples, mean = 0.0 (flags = 0x41) [#]
0  -O                                                                        (1 = 100.0%)
1  ...

- Histogram: Media.FrameReadBackCount.MediaFoundationRenderer recorded 1 samples, mean = 2699.0 (flags = 0x41) [#]
0     ...
2008  -O                                                                        (1 = 100.0%) {0.0%}
2786  ...

// chrome://flags/#enable-media-foundation-clear disabled:
- Histogram: Media.DroppedFrameCount2.RendererImpl.Clear recorded 1 samples, mean = 0.0 (flags = 0x41) [#]
0  -O                                                                        (1 = 100.0%)
1  ...

- Histogram: Media.DroppedFrameCount2.RendererImpl.Encrypted recorded 1 samples, mean = 0.0 (flags = 0x41) [#]
0  -O                                                                        (1 = 100.0%)
1  ...

- Histogram: Media.FrameReadBackCount.RendererImpl recorded 1 samples, mean = 1084.0 (flags = 0x41) [#]
0     ...
1043  -O                                                                        (1 = 100.0%) {0.0%}
1447  ...
```

Bug: 1258887
Change-Id: I23c1e81aef66e9bd555fbd2dc0add61a610bd7e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3501242
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Frank Li <frankli@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#978997}
3 files changed
tree: 7830dff5e8105c6cf57a9f88331e522bec3eca6f
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  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.