New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 599135 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 569615
issue 552472
issue 599128



Sign in to add a comment

Marks for performance timing events should be issued after the fact

Project Member Reported by charliea@chromium.org, Mar 30 2016

Issue description

See://crbug.com/569615#c4 for lots of context.

TL;DR right now, we're issuing marks for performance timing events as the page loads. Instead, we should be issuing those marks after the page is loaded. This will allow us to issue marks for more of these performance timing and have more accurate marks for the ones that we already handle.

 
Start for all progress 
Components: Speed>Tracing
Components: -Internals>Tracing
Cc: charliea@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
I'm unassigning myself from this. It's a pretty nontrivial bug that doesn't really align well with my primarily power-related goals right now, and I don't think I'll get to this bug any time soon.
Status: Available (was: Untriaged)
Owner: tdres...@chromium.org
Status: Started (was: Available)
I'm planning to dispatch these during idle time.
Cc: tdres...@chromium.org
Components: -Blink>PerformanceAPIs
Owner: ----
Status: Untriaged (was: Started)
Er, I think I misread this originally.

Looks like this is more of a tracing issue than a web perf issue.

Marking untriaged.

Sign in to add a comment