gildekel@chromium.org chromeos-gfx-display@chromium.org Modeset attempt result of an external display. Every time an external display is connected/disconnected, or when the display mode of the external screen is changed by the user, Chrome attempts to modeset the display. This metric tracks the result of those attempts. Resolution and RefreshRate metrics will be recorded for each attempt. gildekel@chromium.org chromeos-gfx-display@chromium.org Modeset attempt result of an external display. This is recorded after Chrome attempted all the available modes and finally modeset the display. All the previously attempted modes and refreshes, including the successful one will be recorded. gildekel@chromium.org chromeos-gfx-display@chromium.org Modeset attempt result of an internal display. Chrome might try additional modes after a failed attempt. Every time an external display is connected/disconnected, or when the display mode of the external screen is changed by the user, Chrome attempts to modeset the display. This metric tracks the result of those attempts. Resolution and RefreshRate metrics will be recorded for each attempt. gildekel@chromium.org chromeos-gfx-display@chromium.org Modeset attempt result of an internal display. This is recorded after Chrome attempted all the available modes and finally modeset the display. All the previously attempted modes and refreshes, including the successful one will be recorded. gildekel@chromium.org chromeos-gfx-display@chromium.org The final result of a configuration attempt across all displays. This is recorded every time Chrome configures all connected displays, or fails to do so after exhausting all available modes in one (or more) of the displays. Partial success occurs when a configuration is successful, but not with the requested resolution/refresh rate for one (or more) of the connected displays (e.g. a display fails to modeset at 4k@60Hz, but succeeds at 1440p@60Hz). gildekel@chromium.org chromeos-gfx-display@chromium.org Total number of external displays connected via MST and being configured. This is recorded every time an external display is connected/disconnected, or when the display mode of a screen is about to change. gildekel@chromium.org chromeos-gfx-display@chromium.org Percentage of external displays connected via MST and being configured. This is recorded every time an external display is connected/disconnected, or when the display mode of a screen is about to change. sukoo@google.com chromeos-gfx-compositor@google.com Number of fallback CRTC-Connector permutations attempted after initial test modeset failure with {NumDisplays} connected. All permutations after success are not counted. sukoo@google.com chromeos-gfx-compositor@google.com The outcome of test-only modeset configuration request. If a test modeset initially fails, but succeeds on fallback, then it will be counted as FallbackSuccess. gildekel@chromium.org chromeos-gfx-display@chromium.org Total number of external displays being configured. This is recorded every time an external display is connected/disconnected, or when the display mode of a screen is about to change. gildekel@chromium.org chromeos-gfx-display@chromium.org Tracks an {Connection} display's resulting refresh rate after a successful display configuration. gildekel@chromium.org chromeos-gfx-display@chromium.org {Connection} {Report} gildekel@chromium.org chromeos-gfx-display@google.com The type of serial number retrieved from block zero of a display's EDID during EDID parsing. gildekel@chromium.org chromeos-gfx-display@google.com The number of serial numbers provided in an EDID (i.e. via block zero and/or the serial number descriptor block). Values should be in the range of 0-2. gildekel@chromium.org chromeos-gfx-display@google.com The availability (or lack thereof) of tracked optional fields during EDID parsing of external. gildekel@chromium.org chromeos-gfx-display@google.com Whether or not multiple connected displays produced identical display IDs due to incomplete EDIDs. This may occur when identical displays (same make and model) lack serial numbers in both the EDID's block zero or S/N descriptor block. Recorded every time Chrome OS detects a change in display configuration and attempts to get an updated list of available displays. gildekel@chromium.org chromeos-gfx-display@google.com Type of failure that occurs during EDID parsing. Typically the failure is caused by a mismatch between the EDID size and the expected offset of the data component. boliu@chromium.org vasilyt@chromium.org chrome-gpu-metric-alerts@google.com Recordes whether the eglDupNativeFenceFDANDROIDFn function is exported. Recorded once on eglDisplay init, which is basically once on GPU process start. geofflang@google.com angle-team@google.com An extended Windows error code returned from D3D11CreateDevice on error when ANGLE's D3D backend is in use. Can be almost any valid HRESULT or DXGI error code, which are listed at https://msdn.microsoft.com/en-us/library/windows/desktop/bb509553.aspx. geofflang@google.com angle-team@google.com The maxmium supported (or currently requested) Direct3D feature level in D3D11 ANGLE. We support as low as 9.3, and as high as 11.1, though Chrome should only use 10.0+ for D3D11. Gives an indication of how new a user's video card is, what features it supports, and it's general speed tier. Recorded on D3D device initialization, loss, or reset when ANGLE's D3D backend is in use. geofflang@google.com angle-team@google.com The result from initializing a D3D11 device in ANGLE. Can be success, or one of several error codes which indicate different reasons for failing. Recorded on D3D11 device initialization when ANGLE's D3D backend is in use. geofflang@google.com angle-team@google.com The result from initializing a D3D9 device in ANGLE. Can be success, or one of several error codes which indicate different reasons for failing. Recorded on D3D9 device initialization when ANGLE's D3D backend is in use. geofflang@chromium.org angle-team@google.com Error codes received when checking for D3D device removal reason. HRESULT is DXGI error code that listed at https://learn.microsoft.com/en-us/windows/win32/api/d3d11/nf-d3d11-id3d11device-getdeviceremovedreason geofflang@chromium.org angle-team@google.com The size of compiled D3D shader bytecode. geofflang@chromium.org angle-team@google.com The time it takes for fxc to compile HLSL to D3D bytecode. Recorded for all clients regardless of support for high resolution timers. NOTE: metric expired from 2025-01-05 to 2025-10-09. geofflang@chromium.org angle-team@google.com The time it takes for the Metal driver to compile a shader with the newLibraryFromSource function. Recorded for all clients regardless of support for high resolution timers. blundell@chromium.org geofflang@chromium.org vasilyt@chromium.org angle-team@google.com Tracks the amount of time that it took for WebView to save HWUI's GL state when using ANGLE. Recorded once per saving of HWUI state when drawing with GL. Recorded for all clients as ANGLE does not support checking for high-resolution clocks (in practice, all Android devices have high-resolution clocks). Note: Expired on June 1 2024 and revived on June 10 2024. blundell@chromium.org chrome-gpu-metric-alerts@google.com Records whether ANGLE is able to emulate GLES3 on desktop platforms. Recorded once per GPU process launch. vmiura@chromium.org kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org One or more entries are recorded to this histogram after each succesful GPU process launch. Each GPU blocklist entry, contained in software_rendering_list.json, that applies has the entry id recorded. Additionally the value 0, which doesn't correspond to a blocklist entry, is always recorded once to provide a denominator to calculate percentages. vmiura@chromium.org kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org Counts number of browser invocations for which a GPU feature is allowed/blocklisted/disabled. vasilyt@chromium.org nazabris@microsoft.com jochin@microsoft.com Records, during GPU process initialization, the combination of the following two features being enabled/disabled: 1) Accelerated 2D Canvas 2) OOP Rasterization of Canvas. kylechar@chromium.org Records what compositing mode (software, GL, etc.) Chrome is using every five minutes. This is the default compositing mode that most windows will use. There are some window types (eg. menus on some platforms) that always use software compositing and ignore the default. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Records the SharedImageBackingType to which data is copied during content synchronization within CompoundImageBacking. This helps identify the destination of data in copy operations. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Records the initial SharedImageUsage of the CompoundImageBacking when a content synchronization (copy) occurs. This helps identify if specific initial usage configurations are prone to excessive copying. Recorded as a sparse histogram of the usage bitmask. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Records the reason a content synchronization (copy) operation occurred within CompoundImageBacking. This distinguishes between copies triggered by stale data reads and those for synchronization before a write operation. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Records the SharedImageBackingType from which data is copied during content synchronization within CompoundImageBacking. This helps identify the source of data in copy operations. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Success rate of content synchronization (copy) operations within CompoundImageBacking. This metric indicates whether data transfer between different backing types completed without errors. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Records the SharedImageAccessStream that triggered a content synchronization (copy) operation within CompoundImageBacking. This provides insight into which access patterns necessitate data copies. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Records the SharedImageAccessStream that triggered a dynamic allocation of a new backing within a CompoundImageBacking. This provides insight into which types of access patterns are causing dynamic allocations. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Records the type of the new SharedImageBacking that was dynamically allocated. This helps understand the type of backings being allocated at runtime. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Records the initial SharedImageUsage of the CompoundImageBacking when a dynamic allocation occurs. This helps identify which initial usage configurations are most likely to require additional backings later. Recorded as a sparse histogram of the usage bitmask. vikassoni@chromium.org chrome-gpu-metric-alerts@chromium.org Records the maximum number of SharedImageBacking elements allocated within a CompoundImageBacking instance during its lifetime. This metric is recorded once in the destructor. It helps to track and fine tune peak memory consumption by this backing. jonross@chromium.org chrome-gpu-metric-alerts@chromium.org The reason a GPU command buffer context of a given type was lost. zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Records the highest D3D_FEATURE_LEVEL available, collected in the info collection GPU process, once per UMA ping. This is Windows platform only. magchen@chromium.org zmo@chromium.org The maximum D3D12 feature level supported in the gpu drivers. It is recorded in the browser process 120 seconds after the browser launch. magchen@chromium.org zmo@chromium.org amaiorano@google.com The maximum supported D3D shader model version on a D3D12 device. It is recorded in the browser process 120 seconds after the browser launch. Note that the "2" suffix was added when a fix was made in how this stat is collected: the previous unsuffixed version would store "unknown/unsupported" on systems that supported shader model 5.1 to 6.5, but were unaware of 6.6. The suffixed version correctly stores the highest supported shader model. geofflang@google.com angle-team@google.com ANGLE's currently active D3D shader model version. Logged once every startup of the GPU process, on Windows only. Note that Shader Models 2 and 3 map to D3D9 with ANGLE, and 4+ map to D3D11 ANGLE. kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org Tracks whether the Dawn device used by Graphite supports Core or Compatibility level. enga@chromium.org mdb.webgpu-dev-team@google.com Measures the time to collect Dawn information during GPU info collection. NOTE: metric expired from 2024-06-25 to 2025-05-01. vasilyt@chromium.org tangm@microsoft.com Records the duration of CommitAndClearPendingOverlays, which contains the work to update the DCLayerTree's visual contents, visual tree, and commit. This estimates the amount of work DCLayerTree needs to do per frame and can be used to compare incremental tree updating algorithms. Only reported on systems which have high resolution timers. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org How the Desktop Window Manager presented Chrome's DirectComposition layers of video or canvas elements to the screen. Only recorded on Windows. NOTE: This metric was expired and not collecting data between 2021-12-31 and crrev.com/c/4041850 (M110). magchen@chromium.org zmo@chromium.org The number of YUV overlays we are going to present in each frame if the number is not 0. Recorded when the overlay processor is called for drawing a frame. magchen@chromium.org zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Recorded for each quad (on overlay processing) the reason it was or wasn't put in an overlay. Reported for Texture quad type. Warning: this histogram was expired from 2022-05-01 to 2022-06-24 and again from 2023-08-20 and 2023-12-21; data may be missing. magchen@chromium.org zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Recorded for each quad (on overlay processing) with protected video type the reason it was or wasn't put in an overlay. vasilyt@chromium.org tangm@microsoft.com Records the duration of IDCompositionDevice2::Commit, which is the subset of GPU.DirectComposition.CommitAndClearPendingOverlaysDuration that only contains the DComp commit portion. This allows us to estimate how much of the former can be attributed to DComp internals vs DCLayerTree. Only reported on systems which have high resolution timers. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org True if the GPU driver supports hardware overlays. Recorded during Chrome GPU initialization and each time the overlay caps change. magchen@chromium.org zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Recorded for each video quad during the video playback whether it is an underlay or an overlay. magchen@chromium.org zmo@chromium.org magchen@chromium.org Which overlay format was chosen for YUV overlays. Recorded once per GPU process launch only if hardware overlays are supported. (Might be lack of metrics coverage between 2022-05-01 and 2022-06-24 due to metric expiration.) magchen@chromium.org zmo@chromium.org magchen@chromium.org True if Chrome will try to use DirectComposition overlays. (Might be lack of metrics coverage between 2021-10-04 and 2022-06-24 due to metric expiration.) lehoangquyen@chromium.org chrome-gpu-metric-alerts@chromium.org Records whether Direct Composition is supported. Recorded on GPU process startup. magchen@chromium.org zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Whether creating swap chain for protected video succeeded. Recorded once per swap chain creation. magchen@chromium.org zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Whether creating swap chain for protected video succeeded. Recorded once per swap chain creation. magchen@chromium.org zmo@chromium.org magchen@chromium.org What format was used for each overlay swap chain on each swap buffers. (Might be lack of metrics coverage between 2020-12-31 and 2022-06-24 due to metric expiration.) magchen@chromium.org zmo@chromium.org magchen@chromium.org What code path was used to present a video frame. Recorded on each present. (Might be lack of metrics coverage between 2022-03-06 and 2022-06-24 due to metric expiration.) magchen@chromium.org chrome-gpu-metric-alerts@chromium.org Whether DrDC (Direct Rendering Display Compositor) is enabled or not. Recorded when CompositorGpuThread is created in GpuServiceImpl. vmiura@chromium.org kbr@chromium.org zmo@chromium.org For every entry in the gpu driver bug list that is hit on a machine, this records the id. Entry 0 is the total number of times that data is recorded. It should be recorded whenever new GPU information is received: on startup, whenever a GPU process launches, and whenever the active GPU changes. rakina@chromium.org chrome-webium-product-eng@google.com Records whether the renderer's WidgetBase successfully used the initial CompositorFrameSink pipes provided by the browser instead of requesting creation of new pipes. Logged when WidgetBase initializes its LayerTreeFrameSink. zmo@chromium.org chrome-gpu-metric-alerts@chromium.org The display type used to ask for an EGLDisplay. alemate@chromium.org magchen@chromium.org oshima@chromium.org Records the duration of EnsureWorkVisible GPU call. Since it's blocking UI thread we want to measure it, and this histogram must be active as long as this call is still blocking. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. One some clients this metric will be logged only one time out of one thousand to reduce the overhead of taking the metric. alemate@chromium.org magchen@chromium.org oshima@chromium.org Records the duration of EnsureWorkVisible GPU call. Since it's blocking UI thread we want to measure it, and this histogram must be active as long as this call is still blocking. This is a sister histogram to GPU.EnsureWorkVisibleDuration. The former is our target goal. However it's custom buckets do not have enough granularity to measure improvement steps. This metric will instead cap at 5s, and allow the buckets to give us better visibility into the 15ms-250ms interval ranges. We will use this one until we improve the blocking call. One some clients this metric will be logged only one time out of one thousand to reduce the overhead of taking the metric. rakina@chromium.org chrome-webium-product-eng@google.com The time it takes for the browser process to establish the GPU channel for a renderer (either via Mojo invitation or standard callback). Measured from the start of the GpuClient request to when the channel is successfully established with the GPU process. rakina@chromium.org chrome-webium-product-eng@google.com Measures the time from the earliest request in a batch until the channel is established. Logged once per channel establishment upon successful completion. rakina@chromium.org chrome-webium-product-eng@google.com Measures the wait time for each individual request in a batch to establish the GPU channel. Logged for every request in the batch upon successful completion. rakina@chromium.org chrome-webium-product-eng@google.com The total time it takes to establish the initial GPU channel for a new renderer process. Measured from the moment the browser process starts the request (in GpuClient) to the moment the renderer process finishes initializing the channel (including getting the GPU info). rakina@chromium.org chrome-webium-product-eng@google.com Measures the total time from renderer initialization to GPU channel establishment. Logged once per renderer process initialization when the channel establishment completes successfully. fangzhoug@chromium.org kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org Records the result of retrying EstableGpuChannelSync in Chrome OS. Logged every time when a EstableGpuChannel fails on Chrome OS. cduvall@chromium.org jam@chromium.org Measures the time it takes to synchronously establish the GPU channel. Logged every time a sync call to EstableGpuChannelSync is made and a channel is not already available. chikamune@chromium.org kouhei@chromium.org chrome-gpu-metric-alerts@chromium.org Measures the time it takes to synchronously establish the GPU channel. Logged on the first run of a sync call to EstableGpuChannelSync is made. blundell@chromium.org chrome-gpu-metric-alerts@google.com Recorded once for every GPU launch mode fallback event. Records the cause of the fallback event. jonross@chromium.org chrome-gpu-metric-alerts@chromium.org Counts the number of GpuFenceHandle clone calls between (post) submits. vasilyt@chromium.org yzshen@chromium.org chrome-gpu-metric-alerts@chromium.org Records the command buffer namespace when TaskGraph validation forcefully releases fence sync. vasilyt@chromium.org yzshen@chromium.org chrome-gpu-metric-alerts@chromium.org Records the cause of calls to SyncPointManager::EnsureFenceSyncReleased() for releasing fence sync. This histogram is ~1/100 sub-sampled. rakina@chromium.org chrome-webium-product-eng@google.com Measures the wait time from when the renderer is ready to establish the frame sink (in FinishRequestNewLayerTreeFrameSink) until it receives the first BeginMainFrame. Logged when the first frame arrives on the frame sink. magchen@chromium.org zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Records the OpenGL implementation mode. Recorded during GPU process initilization. magchen@chromium.org zmo@chromium.org chrome-gpu-metric-alerts@chromium.org The time between the GPU process start and the collection of GPU info during the process's startup phase. The time range is between 5ms and 90s. Emitted after the collection of GPU info. Reported for all clients. This metric is similar to GPU.GPUInitializationTime.V3, but there are two main differences. First, the range for GPU.GPUInitializationTime.V4 is capped at 90s while the range of the other metric is capped at 5s. Second, this metric is emitted earlier in the execution because this metric is recorded at the same time as trace events which require the timestamp marking the start and end of the GPU initialization to be in scope, whereas V3 only requires the time spent. zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Counts for the exit codes returned by the GPU process when it terminated. vmiura@chromium.org Startup time of the GPU process as measured by the GPU process host. jonross@chromium.org msisov@igalia.com chrome-gpu-metric-alerts@chromium.org The reason a GPU process is terminated. It works only when TERMINATION_STATUS_PROCESS_WAS_KILLED TerminationStatus is set. The goal of this histogram is to get spikes of the above mentioned case when Ozone/Wayland terminates the GPU process due to invalid data it received if any. NOTE: this metric was expired from 2019-08-14 to 2022-11-30 and was brought back by crrev.com/c/4040947. vmiura@chromium.org Counts for each time the GPU Process Host detects the process dies. blundell@chromium.org kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org For each request of an image from GraphiteImageProvider, records whether the image was found in the cache or needed to be created. kylechar@chromium.org michaelludwig@google.com chrome-gpu-metric-alerts@chromium.org The return value for each Graphite insertRecording call made by Chromium. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org The duration of each Graphite context submit call in SkiaOutputDevice in microseconds. This is subsampled at 1%. Only reported on platforms supporting high-resolution clocks. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org The duration of each Graphite context submit call in microseconds. This is subsampled at 1%. Only reported on platforms supporting high-resolution clocks. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org Tracks the average lock acquisition time (in microseconds) for the Dawn device lock. Computed and emitted on every 100th lock acquisition on each Dawn device as the average of the previous 100 lock acquisition durations. Only reported on platforms supporting high-resolution clocks. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org Tracks the maximum lock acquisition time (in microseconds) for the Dawn device lock. Computed and emitted on every 100th lock acquisition for each Dawn device as the maximum of the previous 100 lock acquisition durations. Only reported on platforms supporting high-resolution clocks. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org Records the time spent waiting to acquire the lock in GraphiteSharedContext. Recorded when AutoLock is created. This is subsampled at 1%. Only reported for platforms supporting high resolution clocks. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org Records the time spent waiting to acquire the lock in GraphiteSharedContext when the thread holding the lock was in insertRecording. Recorded when AutoLock is created. This is subsampled at 1%. Only reported for platforms supporting high resolution clocks. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org Records the time spent waiting to acquire the lock in GraphiteSharedContext when the thread holding the lock was in submit or submitAndFlushBackend. Recorded when AutoLock is created. This is subsampled at 1%. Only reported for platforms supporting high resolution clocks. vasilyt@chromium.org yzshen@chromium.org chrome-gpu-metric-alerts@chromium.org For each graph validation of TaskGraph, records the time it takes in milliseconds. vasilyt@chromium.org yzshen@chromium.org chrome-gpu-metric-alerts@chromium.org For each graph valiation of TaskGraph, records whether it finds invalid waits that require forceful release. geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org Time to compile and resolve a Skia OpenGL shader in microseconds. Only reported on systems which have high resolution timers. geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org Time to link and resolve a Skia OpenGL program in microseconds. Only reported on systems which have high resolution timers. geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org If the GrShaderCache is in use. Recorded at GPU channel manager creation. zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Records if GPU hardware acceleration is explicitly disabled by the user. Recorded when the browser process launches. Warning: this histogram was expired from 2022-01-30 to 2022-04-29, and then from 2024-06-30 to 2026-03-27; data may be missing. kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org Records if a device can support running on Vulkan. This value is decided after the first successful GPU service launch and remains constant. If the device doesn't attempt to use Vulkan (eg. it's blocklisted or disabled) or Vulkan compatibility checks fail this will be false. This is recorded with every ongoing UMA log record, except if the UMA record is finalized before the first successful GPU service launch. This should be uncommon. This metric is NOT recorded in records that reflect information from a previous session (i.e., "stability records" or "persistent UMA" data related to the previous session but not uploaded during the previous session). zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Records whether the system has a discrete GPU, collected in the info collection GPU process, once per UMA ping. This is Windows platform only. Warning: this histogram was expired from 2020-04-24 to 2022-04-29; data may be missing. rakina@chromium.org chrome-webium-product-eng@google.com Records whether the initial GPU channel was successfully established and created the GpuChannelHost with correct GPU info. Logged once per renderer process initialization when the channel establishment completes. zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Records the highest Intel GPU generation of the system using the GPU info collected at GPU process startup time, once per UMA ping. magchen@chromium.org zmo@chromium.org Records user device's GPU series type. Only recorded on Windows platform at GPU process launch time. Only meaningful with Intel GPUs. vasilyt@chromium.org chrome-gpu-metric-alerts@chromium.org The time that it took to create an IOSurface. Recorded for every IOSurface that's created. This metric is only collected on Mac, which only has high-resolution clocks. magchen@chromium.org ccameron@chromium.org The time that the GPU's main CPU thread spends waiting for previous frames' GPU work to complete. Recorded at every frame. This metric is only collected on Mac, which only has high-resolution clocks. blundell@chromium.org chrome-gpu-metric-alerts@google.com Records the maximum GLES version supported on Android. Recorded once per GPU process launch and recorded only for non-ANGLE due to complexities in obtaining this information for ANGLE. cwallez@chromium.org chrome-gpu-metric-alerts@chromium.org MTLGPUFamilyMac1 is deprecated since macOS 13 and iOS 16. This histograms is meant to gather information so that the WebGPU W3C group can decide whether to drop MTLGPUFamilyMac1 support. The histogram is recorded at GPU process startup time. cwallez@chromium.org chrome-gpu-metric-alerts@chromium.org Read-write textures are not always supported on Metal. This histograms is meant to gather information so that the WebGPU W3C group can decide whether to require support for this feature. The reported tier is the best tier that was found on the system. Meaning that if only one of the GPUs support read-write textures, a non-zero tier will be reported. The histogram is recorded at GPU process startup time. zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Nvidia device IDs from multi-gpu devices. Recorded when GPU process launches and sends GPUInfo to browser process. vasilyt@chromium.org tangm@microsoft.com A count of the number of OS compositor layers that were dirtied in a single commit. This estimates the amount of work the OS compositor needs to do per frame and can be used to compare incremental tree updating algorithms. hubbe@chromium.org cassew@chromium.org media-dev-uma@chromium.org Records if any connected monitor is HDR capable. Recorded when the gpu process starts. Only recorded on Windows as of M-61. If monitor enumeration fails, this metric will not be provided. kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org Records if graphite::Recording to draw a render pass was successfully inserted into the graphite::Context. Recorded for each insertRecording() call made with a render pass recording. magchen@chromium.org ccameron@chromium.org chrome-gpu-metric-alerts@chromium.org The time that the GPU's main CPU thread spends producing pending CALayer tree on Mac. Recorded when Skia output surface schedules overlays at every frame. This metric is only collected on Mac, which only has high-resolution clocks. jonross@chromium.org chrome-gpu-metric-alerts@chromium.org Records the reason why the deserialization of a PaintOp failed. Recorded in PaintOpReader::Read* methods when the decoding a paint op fails. These failures are typically caused by an invalid or unexpected state or invalid serialized data. geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org mdb.webgpu-dev-team@google.com Records if any existing persistent cache databases were deleted due to incompatible versions. Recorded on GPU process launch. geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org mdb.webgpu-dev-team@google.com Records the size of cache entry keys added to the cache. Subsampled to 1/100. lehoangquyen@chromium.org chrome-gpu-metric-alerts@chromium.org mdb.webgpu-dev-team@google.com Time it takes in gpu::GpuPersistentCache::LoadData (only when it is ready). Recorded only for clients that support high-resolution clocks. geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org mdb.webgpu-dev-team@google.com Records the results of gpu::GpuPersistentCache::Load for determining cache hit rates. geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org mdb.webgpu-dev-team@google.com Records various usages of GpuPersistentCache metadata for calculating rates of load and stores. kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org mdb.webgpu-dev-team@google.com Time it takes in gpu::GpuPersistentCache::StoreData (only when it is ready). Recorded only for clients that support high-resolution clocks. geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org mdb.webgpu-dev-team@google.com Records the size of cache entry values added to the cache. Subsampled to 1/100. kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org Records the size of the serialized VkPipelineCache that is loaded from the cache. lehoangquyen@chromium.org chrome-gpu-metric-alerts@chromium.org mdb.webgpu-dev-team@google.com Whether the gpu::GpuPersistentCache is ready when {LoadStore}Data() is called. Recorded only for first 100 {LoadStore}. magchen@chromium.org vmiura@chromium.org chrome-gpu-metric-alerts@chromium.org Recorded when a display frame is swapped in Viz. It records whether the current frame is handling interaction, animation, both, or none. magchen@chromium.org vmiura@chromium.org chrome-gpu-metric-alerts@chromium.org The VSync callback delay from the system CVDisplayLink or CADisplaylink source to CrGpuMain. Recorded once per frame when OnVSyncPresentation is called. This histogram is ~1/1000 sub-sampled under the CPU reduction experiment. The recorded delay is capped to the maximum of 33 ms. This metric is only for Mac clients with high-resolution clocks. kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org GPU process lifetime as measured by GPU process host. vmiura@chromium.org Recorded once for every GPU process launch and crash when GPU process is started for hardware accelerated GPU compositing and/or WebGL. Crash buckets are based on crash count for disabling features. With OOP-D enabled the display compositor also runs in the GPU process. vmiura@chromium.org Recorded once for every GPU process launch and crash when GPU process is started for SwiftShader WebGL. Crash buckets are based on crash count for disabling features. With OOP-D enabled the display compositor with software compositing will also run as part of the GPU process. Note this was expired from 2024-12-08 to 2015-03-13. vasilyt@chromium.org chrome-gpu-metric-alerts@chromium.org Time it takes for RasterDecoderImpl::FlushSurfaces() to complete. Recorded for the first 100 flushes. olivierli@chromium.org fdoray@chromium.org The result of requesting a WebGPU adapater. Recorded for each attempt. akhna@google.com chromeos-hardening@google.com A boolean that indicates whether sandboxing is successfully applied. A value of true means the GPU is sandboxed. A value of false means the GPU is not sandboxed. Recorded once per GPU process start-up in gpu_init.cc. magchen@chromium.org chrome-gpu-metric-alerts@google.com Records the percentage of time each GPU scheduler task spent executing while at least one other task was also executing on another thread. vikassoni@chromium.org chrome-gpu-metric-alerts@google.com Records the wall time for GPU Scheduler task at various stages and with various priorities. Only recorded for clients with high resolution clocks. Note that the histograms for GPU.Scheduler.{Stage} was expired on 2022-08-07 and was re-enabled on 2023-11-17. It was then expired again on 2024-08-07 and was re-enable on 2026-04-15. vikassoni@chromium.org chrome-gpu-metric-alerts@google.com Whether or not the shader prefix loaded from disk matched the expected prefix for the data and system configuration. False indicates either disk corruption or a system configuration change, and should be rare. kylechar@chromium.org chrome-gpu-metric-alerts@google.com Records the type of each SharedImageBacking that's initialized/registered. hitawala@chromium.org chrome-gpu-metric-alerts@chromium.org Records whether a single-channel 16-bit half-float texture (R_F16) fell back to LUMINANCE_F16 because the OpenGL ES context lacks ES3 or half-float linear filtering support. Recorded when getting GL format info for a plane during backing creation. hitawala@chromium.org chrome-gpu-metric-alerts@chromium.org Records whether a single-channel 8-bit texture (R_8) fell back to ALPHA_8 because the OpenGL context lacks ext_texture_rg support. Recorded only for single-channel 8-bit planes (R_8) of a multi-planar texture and only when getting GL format info for such textures during GL based backing creation. hitawala@chromium.org chrome-gpu-metric-alerts@chromium.org Records the SharedImageFormat type for a SharedImageBacking that's initialized/registered. kylechar@chromium.org chrome-gpu-metric-alerts@google.com Records what backend Skia is initialized with for compositing/rasterization in the GPU process. This is only recorded the first time Skia is initialized per GPU process launch, in case it's initialized on more than one thread or reinitialized on context loss. zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Collects whether Chrome uses software renderer or hardware GPU 20 seconds after Chrome starts, and records this value once per UMA ping. This value is not re-collected at each recording time because GPU process could crash for various reasons and fall back to software rendering. This value is intended to reflect device capabilities rather than the current state. boliu@chromium.org chrome-gpu-metric-alerts@chromium.org Whether a transfer cache entry is found when trying to retrieve it. Recorded on every transfer cache look up. boliu@chromium.org chrome-gpu-metric-alerts@chromium.org When a transfer cache is found, record max historical time between reuses. Recorded on every successful transfer cache look up. boliu@chromium.org chrome-gpu-metric-alerts@chromium.org When a transfer cache entry is deleted, record how many times it was used. Recorded when an entry is deleted. boliu@chromium.org chrome-gpu-metric-alerts@chromium.org When a transfer cache is found, record the time since last use. Recorded on every successful transfer cache look up. Expired from 2025-06-22 to 2026-03-24. boliu@chromium.org chrome-gpu-metric-alerts@chromium.org When a transfer cache entry is deleted, record the last time the entry was used. Recorded when an entry is deleted. Expired from 2025-06-22 to 2026-03-30. hitawala@chromium.org kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org Duration of vkCreateGraphicsPipelines call. Recorded every time Ganesh-Vulkan or Graphite-Dawn-Vulkan on Skia context creates graphics pipeline. Only reported for platforms supporting high resolution clocks. hitawala@chromium.org kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org Duration of vkQueueSubmit call. Recorded every time Ganesh-Vulkan or Graphite-Dawn-Vulkan on Skia context submits to vulkan queue. Only reported for platforms supporting high resolution clocks. magchen@chromium.org zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Recorded for each time the GPU watchdog thread starts, crashes and ends. magchen@chromium.org zmo@chromium.org chrome-gpu-metric-alerts@chromium.org Recorded timeout events when the GPU watchdog enters OnWatchdogTimeout. geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org Types of EGL displays used to back WebGL contexts. Recorded at context creation time in the GPU process. lehoangquyen@chromium.org chrome-gpu-metric-alerts@google.com Tracks the amount of time in microseconds it takes to create a D3D11 {ShaderType} shader. Recorded only for clients that support high-resolution clocks. blundell@chromium.org geofflang@chromium.org chrome-gpu-metric-alerts@chromium.org For each load of an entry from {CacheType}, records whether the entry was found in the cache. Expired on June 1 2024 and revived on June 11 2024. enga@chromium.org mdb.webgpu-dev-team@google.com Tracks whether a call to Create{Module} was successful, excluding when the result is found in frontend cache. enga@chromium.org mdb.webgpu-dev-team@google.com Tracks the amount of time in microseconds it takes for a call to Create{Module} to complete, excluding when the result is found in frontend cache. Recorded only for clients that support high-resolution clocks. cwallez@google.com mdb.webgpu-dev-team@google.com Error codes received when checking for D3D device removal reason. HRESULT is DXGI error code that listed at https://learn.microsoft.com/en-us/windows/win32/api/d3d11/nf-d3d11-id3d11device-getdeviceremovedreason cduvall@chromium.org mdb.webgpu-dev-team@google.com Records whether WebGPU or Graphite Dawn has any GPU adapters available. This is recorded during GPU process startup. cduvall@chromium.org mdb.webgpu-dev-team@google.com Records the maximum storage buffer binding size if {AdapterType} GPU is available. This is recorded during GPU process startup. cduvall@chromium.org mdb.webgpu-dev-team@google.com Records the maximum 2D texture dimensions if {AdapterType} GPU is available. This is recorded during GPU process startup. cwallez@google.com enga@google.com kainino@google.com mdb.webgpu-dev-team@google.com WebGPU or Graphite Dawn support level. Recorded on GPU info collection a couple minutes after browser startup. Compatibility mode support means that WebGPU or Graphite Dawn is supported on a non-core backend like OpenGLES. Core backends can always support compatibility mode so compat-on-core-adapter is not reported in this metric. Supported means at least one adapter of that type was available. Blocklisted means all adapters of that type were blocklisted. None means that no adapters of that type were available. Software adapters are considered as None in this metric. hitawala@chromium.org kylechar@chromium.org mdb.webgpu-dev-team@google.com Tracks the amount of time in microseconds it takes for a call to vkQueueSubmit to complete. Recorded only for clients that support high-resolution clocks. lokokung@google.com mdb.webgpu-dev-team@google.com Tracks the amount of time in microseconds it takes for a cached call to {Cacheable} to complete without error when we have a cache hit. This includes the load time from the cache and time to deserialize the result. Recorded only for clients that support high-resolution clocks. lehoangquyen@google.com mdb.webgpu-dev-team@google.com Tracks the number of cache hits for {Cacheable} for the 1st Presentation. Recorded only for clients that support high-resolution clocks. lehoangquyen@google.com mdb.webgpu-dev-team@google.com Tracks the percentage of cache hits for {Cacheable} for the 1st Presentation. Recorded only for clients that support high-resolution clocks. lehoangquyen@google.com mdb.webgpu-dev-team@google.com Tracks the percentage of cache hits for {Cacheable} within 90 seconds of browser start up. Recorded only for clients that support high-resolution clocks. lokokung@google.com mdb.webgpu-dev-team@google.com Tracks the amount of time in microseconds it takes for a cached call to {Cacheable} to complete without error when we have a cache miss. This includes the time necessary to create the results of {Cacheable} from scratch, but does not include the time taken to write the results back into the cache. Recorded only for clients that support high-resolution clocks. hitawala@chromium.org mdb.webgpu-dev-team@google.com Tracks the amount of time in microseconds it takes for a cached call to {Cacheable}.{CacheHitMiss} to complete without error when we have a cache hit or miss within 90 seconds of browser start up. Based off the {Cacheable}.CacheHit and {Cacheable}.CacheMiss metrics above. Recorded only for clients that support high-resolution clocks. hitawala@chromium.org mdb.webgpu-dev-team@google.com Tracks the number of times calls to {Cacheable}.{CacheHitMiss} are emitted within 90 seconds of browser start up. Recorded only for clients that support high-resolution clocks. hitawala@chromium.org mdb.webgpu-dev-team@google.com Tracks the amount of time in microseconds it takes for a call to {ShaderTiming} to complete, excluding when the result is found in frontend cache. Recorded only for clients that support high-resolution clocks. hitawala@chromium.org chrome-gpu-metric-alerts@chromium.org Records whether zero-copy WebGPU import is supported for a GBM buffer. Logged on GbmBuffer creation and when checking compatibility. reillyg@chromium.org src/services/webnn/OWNERS Record Intel NPU device ID when GPU process launches and sends GPUInfo to browser process. robertphillips@google.com michaelludwig@google.com skia-gpu-team@google.com This reports the number of Pipelines used in a five-minute window. This provides information regarding the size of the optimal Pipeline active set. This is only recorded on clients using both Graphite and Precompilation. It is recorded every five minutes. robertphillips@google.com michaelludwig@google.com skia-gpu-team@google.com Records the number of Pipeline creation races in Skia broken down by the origin (Normal compilation vs Pre-compilation) and which instances won (i.e., made it into the cache before the other one). robertphillips@google.com michaelludwig@google.com skia-gpu-team@google.com Measures the time taken to create a Pipeline in Skia's Dawn backend for {CompilationType} compilations. This is only recorded on clients with high-resolution clocks. robertphillips@google.com michaelludwig@google.com skia-gpu-team@google.com Reports the number of Pipelines that were categorized as {PipelineStatistic}. This is only recorded on clients using both Graphite and Precompilation. It is recorded after a 30 minute delay. egdaniel@google.com michaelludwig@google.com skia-gpu-team@google.com The total amount of memory that the VulkanMemoryAllocator used by Skia's Vulkan backend has allocated. This is GPU memory for VkImages and VkBuffers. Note that the allocator may be shared with other users outside of Skia and this amount includes their uses as well. This is collected each time we request an allocation from Skia. Warning: this histogram was expired from 2024-09-01 to 2025-04-02; data may be missing. magchen@chromium.org ccameron@chromium.org chrome-gpu-metric-alerts@chromium.org The average time delta between the expected BeginFrame time and the actual time of BeginFrame on Mac. Each recorded number is an average result of 3600 frames. It's recorded every 3600 frames when OnBeginFrame or OnTimerTick is called. The max delta is capped to 33 ms. This metric is only for Mac clients with high-resolution clocks. Expired on 2025-08-24 and restarted on 2025-09-09. magchen@chromium.org ccameron@chromium.org chrome-gpu-metric-alerts@chromium.org The time delta between the expected and actual BeginFrame callback times on Mac. It's recorded during the BeginFrameSource callbacks using 0.1% subsampling. This metric is only for Mac clients with high-resolution clocks. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org This metric tracks the IPC (Mojo) latency for forwarding CADisplayLink VSync signals on Mac. The duration is measured from DisplayLinkMacMojo::OnDisplayLinkVSyncCallback() within the Browser process to ExternalBeginFrameSourceMojoMac::IssueExternalVSync() in the GPU process. Recorded once per frame upon the invocation of IssueExternalVSync, This metric is only for Mac clients with high-resolution clocks. aswolfers@chromium.org chromeos-gfx-compositor@chromium.org This is logged once per session of the variable refresh rate (VRR) feature being enabled. This counts the number of BeginFrames which are issued using VRR. magchen@chromium.org vmiura@chromium.org chrome-gpu-metric-alerts@chromium.org The VSync callback delay from the system CVDisplayLink or CADisplaylink source to VizCompositorThread. Recorded once per frame when OnDisplayLinkCallback is called. This histogram is ~1/1000 sub-sampled under the CPU reduction experiment. The recorded delay is capped to the maximum of 33 ms. This metric is only for Mac clients with high-resolution clocks. hitawala@chromium.org vasilyt@chromium.org Records if SurfaceAnimationManager is cached by FrameSinkManagerImpl on Animate. The SurfaceAnimationManager may not be cached if CompositorFrameTransitionDirective::Type::kAnimateRenderer directive is issued before CompositorFrameTransitionDirective::Type::kSave directive is completely processed leading to an incomplete CopyOutputRequest. kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org This is recorded each time SkiaRenderer attempts to create a fallback image to replace a missing shared image. The result captures success and failure with a reason for the failure. jonross@chromium.org chrome-gpu-metric-alerts@chromium.org An enum status result for attempted delegated compositing (success or failure reason) recorded every drawn frame. jonross@chromium.org chrome-gpu-metric-alerts@chromium.org A count of the number of proposed overlay candidates available for overlay selection. Recorded every time a frame is rendered by the display compositor. kylechar@chromium.org chrome-gpu-metric-alerts@chromium.org Overlay strategies used to promote Hardware Overlays, once or more per frame. Recorded every time a frame is rendered by the display compositor, or once per overlay promoted if multiple were promoted. magchen@chromium.org zmo@chromium.org Any root damage excluding overlay damage in the current frame? magchen@chromium.org zmo@chromium.org The root damage type excluding underlay damage in the current frame. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org The result of creating {Source} in the GPU process for each display. Recorded whenever a DisplayLink is created in ExternalBeginFrameSourceMac or ImageTransportSurfaceOverlayMacEGL within the GPU process. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org The time elapsed from when a NeedsBeginFrames(true) request is sent via IPC to the browser process until the first VSync signal is received by the GPU process. This is recorded once per request cycle per display. This is recorded only when the CADisplayLinkInBrowser feature is enabled (which uses ExternalDisplayLink and VSyncProviderMac). lizeb@chromium.org chromeos-gfx@chromium.org Frame interval, as provided in OnBeginFrame() for external sources. Subsampled, but recorded at BeginFrame() time. magchen@chromium.org ccameron@chromium.org chrome-gpu-metric-alerts@chromium.org The result of creating CVDisplaylink in ExternalBeginFrameSourceMac. If successful, BeginFrameSource is driven by HW VSync instead of timer. This histogram does not include the data from DelayBasedBeginFrameSourceMac. It's recorded each time a DisplayLink is created during RootCompositorFrameSinkImpl/ExternalBeginFrameSourceMac creation or during the monitor change in the existing ExternalBeginFrameSourceMac. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org The result of creating CVDisplaylink with CVDisplayLinkCreateWithCGDisplay or CADisplayLink with [screen displayLinkWithTarget] per display. It does not track ExternalDisplayLinkMac or Timer. This histogram is recorded each time a DisplayLink is created in ExternalBeginFrameSourceMac, ImageTransportSurfaceOverlayMacEGL, or DisplayLinkMacMojo. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org The time elapsed from when ExternalBeginFrameSourceMac is constructed to when the first OnDisplayLinkCallback or OnTimerTick is called. This measures the latency to start the first frame using {Source}. This is not recorded if a power event occurs before the first frame. magchen@chromium.org chrome-gpu-metric-alerts@chromium.org The time elapsed from when the first OnNeedsBeginFrames(true) is called to when the first OnDisplayLinkCallback or OnTimerTick is called. This measures the latency from the first request for frames to the first frame delivery using {Source}. This is not recorded if a power event occurs before the first frame. jonross@chromium.org chrome-gpu-metric-alerts@chromium.org Time spent computing the number of active File Descriptors. This is logged once every 5 minutes as the cost of this computation is estimated to be at least 1ms. Warning: This metric does not include reports from clients with low-resolution clocks. jonross@chromium.org chrome-gpu-metric-alerts@chromium.org {FdStat} File Descriptors for the GPU process. This is logged once every 5 minutes as the cost of this computation is estimated to be at least 1ms. kartarsingh@google.com woa-performance-team@google.com Records whether the deadline selected by viz::FrameDeadlineDecider has a presentation delta that is sustainable with the current number of allowed buffers to avoid multiple-vsync swap throttling. Recorded every time a frame is drawn and swapped. kartarsingh@google.com woa-performance-team@google.com Records the reason why a specific frame deadline was selected by viz::FrameDeadlineDecider. Recorded every time a frame is drawn and swapped. boliu@chromium.org chrome-gpu-metric-alerts@chromium.org Record the actual frame rate when FrameIntervalDecider decides system should use its default behavior. Useful as reference histogram for ActualIntervalForXXhz histograms, to see the effect of FrameIntervalDecider deciding on a particular frame rate. Note however it's not a perfect reference since the conditions leading to use system default is not independent from conditions leading a particular frame rate being selected. Recorded every viz frame, sub-sampled with probability 0.001. Note this requires FrameIntervalDecider to be enabled as well as using an ExternalBeginFrameSource. boliu@chromium.org chrome-gpu-metric-alerts@chromium.org For a few common result intervals (named in hz), record the distribution of actual frame intervals. Recorded every viz frame, sub-sampled with probability 0.001. Note this requires FrameIntervalDecider to be enabled as well as using an ExternalBeginFrameSource. boliu@chromium.org chrome-gpu-metric-alerts@chromium.org Frame interval matcher type matched current frame. Recorded every viz frame, sub-sampled with probability 0.001. boliu@chromium.org chrome-gpu-metric-alerts@chromium.org Frame interval decider result interval. Recorded every viz frame but only if the result variant is an interval time delta, sub-sampled with probability 0.001. sashamcintosh@chromium.org chromeos-gfx@chromium.org The time that a begin frame is throttled due to max pending swaps. Recorded when draw and swap executes (only when a frame is throttled). Refer to BeginFrameSource::SetIsGpuBusy for details. Warning: This metric does not include reports from clients with low-resolution clocks. jophba@chromium.org media-capture-dev@chromium.org The time it took from when FrameSinkVideoCapturerImpl sent a request for frame capture until the result becomes available to the capturer. Format-agnostic version of `Viz.FrameSinkVideoCapturer.[NV12/I420].CaptureDuration` histograms. Warning: this histogram was expired from 2023-07-15 to 2026-06-10; data may be missing. jophba@chromium.org media-capture-dev@chromium.org Whether a capture initiated by FrameSinkVideoCapturerImpl succeeded. Format-agnostic version of `Viz.FrameSinkVideoCapturer.[NV12/I420].CaptureSucceeded` histograms. Warning: this histogram was expired from 2023-07-15 to 2026-06-10; data may be missing. jophba@chromium.org media-capture-dev@chromium.org True if the capturer has used a resurrected video frame, thus avoiding having to reserve it from a frame pool, false otherwise. Warning: this histogram was expired from 2023-07-15 to 2026-06-10; data may be missing. jophba@chromium.org media-capture-dev@chromium.org The time it took from when FrameSinkVideoCapturerImpl sent a request for an I420 readback until the result comes back and ReadI420Planes successfully finishes. Warning: this histogram was expired from 2021-03-07 to 2022-03-10; data may be missing. Warning: this histogram was expired from 2024-09-29 to 2026-06-10; data may be missing. jophba@chromium.org media-capture-dev@chromium.org Whether an I420 readback initiated by FrameSinkVideoCapturerImpl succeeded. Warning: this histogram was expired from 2020-12-31 to 2022-03-10; data may be missing. Warning: this histogram was expired from 2025-05-26 to 2026-06-10; data may be missing. jophba@chromium.org media-capture-dev@chromium.org The time it took from when FrameSinkVideoCapturerImpl decided that a new I420 frame needs to be produced to the moment when it was ready to deliver it. This encompasses the `Viz.FrameSinkVideoCapturer.I420.CaptureDuration` time, but also includes time taken to render video capture overlays. Warning: this histogram was expired from 2024-09-29 to 2026-06-10; data may be missing. jophba@chromium.org media-capture-dev@chromium.org The time it took from when FrameSinkVideoCapturerImpl sent a request for an NV12 copy until the result comes back. Note: The histogram logging was adjusted in M102 to align with how `Viz.FrameSinkVideoCapturer.[RGBA/I420].CaptureDuration` histograms behave. After the change, this histogram also started including the time taken to set the color space on a video frame. Warning: this histogram was expired from 2023-07-15 to 2026-06-10; data may be missing. jophba@chromium.org media-capture-dev@chromium.org Whether an NV12 capture initiated by FrameSinkVideoCapturerImpl succeeded. Warning: this histogram was expired from 2023-07-15 to 2026-06-10; data may be missing. jophba@chromium.org media-capture-dev@chromium.org The time it took from when FrameSinkVideoCapturerImpl decided that a new NV12 frame needs to be produced to the moment when it was ready to deliver it. This encompasses the `Viz.FrameSinkVideoCapturer.NV12.CaptureDuration` time. Warning: this histogram was expired from 2023-07-15 to 2026-06-10; data may be missing. jonross@chromium.org viz-team-wat@google.com The time it took from when FrameSinkVideoCapturerImpl sent a request for an RGBA readback until the result comes back and ReadRGBAPlane successfully finishes. jophba@chromium.org media-capture-dev@chromium.org The time it took from when FrameSinkVideoCapturerImpl decided that a new frame needs to be produced to the moment when it was ready to deliver it. This encompasses the `Viz.FrameSinkVideoCapturer.CaptureDuration` time, but also includes time taken to render video capture overlays. Format-agnostic version of `Viz.FrameSinkVideoCapturer.[NV12/I420].TotalDuration` histograms.