This feature is only shown in the feature list to users with edit access.

Adds information about what type of non javascript work is being done by the user agent to samples from the JS Self-Profiling API.

Motivation

Non javascript execution is hard to identify in traces captured with JS Self-Profiling API: From a trace we cannot differentiate idle activity from top level UA activity, so for example code that triggers asynchronous rendering work cannot be measured properly. Long traces may include Garbage Collection activity which cannot be differentiated with javascript execution and adds to the noise on the collected trace.

Status in Chromium

Blink>PerformanceAPIs


No active development

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signals

Owners

Intent to Prototype url

Intent to Prototype thread

Search tags

profiler, profiling, js,

Last updated on 2021-11-15