Telemetry chrome-hang data for Nightly 22 on Windows shows we're getting hangs > 5 seconds while initializing Direct3D on startup. See attachment for hang stacks. Ideas considered: - This is not limited to single-core machines - These hangs aren't exclusive to any specific driver or vendor - The distribution of these hang reports across vendors is roughly 1:1:2 for Intel/Nvidia/AMD. However, the general Telemetry Nightly population has a 1:1:1 ratio for these vendors.

Correction, hang reports have a 2:1:1 distribution across Intel/Nvidia/AMD. The general Telemetry Nightly population (from a single day) has a 1:1:1 ratio for these vendors