New issue
Advanced search Search tips

Issue 693271 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature



Sign in to add a comment

Feature request: a WebRTC specific tracing profile

Project Member Reported by q...@chromium.org, Feb 17 2017

Issue description

Chrome Version: Version 57.0.2987.54 beta (64-bit)

What steps will reproduce the problem?
(1) go to chrome://tracing
(2) click on the "Record" button
(3)

What is the expected result?

a tracing profile that specifically for WebRTC that could help figure out CPU and memory issues there.
 
Screenshot from 2017-02-16 16:01:02.png
109 KB View Download

Comment 1 by q...@chromium.org, Feb 17 2017

Components: Blink>WebRTC>Tools
qaz@: There is a webrtc recording category that records a bunch of traces in WebRTC. Is there anything in particular you're missing?
Owner: tommi@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by tommi@chromium.org, Mar 6 2017

Status: Fixed (was: Assigned)
For CPU related issues, there is already the "webrtc" category as grunell@ points out.
In addition to that, we'll be supporting the memory-infra category more moving forward.

Comment 5 by q...@chromium.org, Mar 6 2017

I was refering to a prebuilt profile that includes multiple categories, such as the existing "Web developer", "Input latency", etc. but for WebRTC.

Sign in to add a comment