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

Issue metadata

Status: Fixed
Owner:
Closed: Dec 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment
link

Issue 912363: performance measures with the same name are reported incorrectly in the trace

Reported by paulir...@chromium.org, Dec 5 Project Member

Issue description

If the page uses performance.measure with the same measure name, trace events are misreported, which lead to incorrect rendering in the devtools timeline (and tracing UI)

For example:
  setTimeout(_ => performance.mark('astart'), 0);
  setTimeout(_ => performance.mark('aend'), 100);

  setTimeout(_ => performance.mark('bstart'), 20);
  setTimeout(_ => performance.mark('bend'),  220);

  setTimeout(_ => performance.mark('cstart'), 40);
  setTimeout(_ => performance.mark('cend'),   41);

  setTimeout(_ => {
    performance.measure('timespan', 'astart', 'aend');
    performance.measure('timespan', 'bstart', 'bend');
    performance.measure('timespan', 'cstart', 'cend');
  }, 250);


This should report measure of length ~100ms, ~200ms, and 1ms, 
However, currently we see measures of: ~220, ~80ms, and 1ms.
 
actual-broken.png
10.9 KB View Download
expected-fixed.png
10.6 KB View Download

Comment 1 by paulir...@chromium.org, Dec 5

Status: Started (was: Untriaged)

Comment 3 by paulir...@chromium.org, Dec 7

Status: Fixed (was: Started)

Comment 4 by alph@chromium.org, Dec 18

Cc: mkretzsc...@google.com alph@chromium.org
 Issue 865780  has been merged into this issue.

Sign in to add a comment