media: Report active display type histograms on hardware-context-reset

With dual GPU devices on Windows, the hardware-context-reset (a.k.a
DRM_E_TEE_INVALID_HWDRM_STATE) is easy to repro and unrecoverable. For
example, 4 test devices with dual GPU setup can repro the same issue.

For further investigation on too many hardware-context-reset error
cases and to find any correlation between dual-gpu setup and this
error, added the following histograms:
- ActiveGpuDisplayInfo: Active GPU's display type whether built-in or
  external
- ActiveGpuVendorId: Active GPU's vendor ID
- NonActiveGpuVendorId: Non-active GPU's vendor ID if exists

for the existing histograms,

- Media.EME.MediaFoundationService.HardwareContextReset
- Media.MediaFoundationRenderer.PlaybackError

We will learn how roughly the devices with dual-GPU or external-display
causes the hardware-context-reset. Plus we can compare them with the
overall playback errors.

Test results: http://shortn/_npZ0EPa9eR

Bug: b:454139099, b:454691291
Change-Id: I2069476d57097c17eabb827dab4da0fbd91c7c05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7229280
Reviewed-by: Evan Liu <evliu@google.com>
Reviewed-by: Maggie Chen <magchen@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Commit-Queue: Sangbaek Park <sangbaekpark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1554771}
3 files changed
tree: af9d00476e1c65c111e7525202ee7220ac1c3ac7
  1. .gemini/
  2. .github/
  3. agents/
  4. android_webview/
  5. apps/
  6. ash/
  7. base/
  8. build/
  9. build_overrides/
  10. buildtools/
  11. cc/
  12. chrome/
  13. chromecast/
  14. chromeos/
  15. codelabs/
  16. components/
  17. content/
  18. crypto/
  19. dbus/
  20. device/
  21. docs/
  22. extensions/
  23. fuchsia_web/
  24. gin/
  25. google_apis/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. net/
  34. pdf/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .cursorignore
  54. .geminiignore
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. CRYPTO_OWNERS
  72. DEPS
  73. DIR_METADATA
  74. LICENSE
  75. LICENSE.chromium_os
  76. OWNERS
  77. PRESUBMIT.py
  78. PRESUBMIT_test.py
  79. PRESUBMIT_test_mocks.py
  80. README.md
  81. SECURITY_OWNERS
  82. 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.