New issue
Advanced search Search tips

Issue 878059 link

Starred by 2 users
Status: Fixed
Owner:
sadrul@chromium.org
Closed: Sep 6
Cc:
nzolghadr@chromium.org
sahel@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2 98th percentile regressed by 43% in M70

Project Member Reported by sahel@chromium.org, Aug 27 
The regression is visible on Canary and Dev (annotated by this bug number):
https://uma.googleplex.com/p/chrome/timeline_v2?sid=9273ce147c234ef158bbc30fd2223082

Here is the change range on Canary: (70.0.3523.0 - 70.0.3525.3)
https://chromium.googlesource.com/chromium/src/+log/70.0.3523.0..70.0.3525.0?pretty=fuller&n=10000

Comment 1 by sahel@chromium.org, Aug 27

Cc: sahel@chromium.org nzolghadr@chromium.org
Labels: OS-Android
Owner: sadrul@chromium.org
Status: Assigned (was: Untriaged)
The report uses 98% since 99% hits the max threshold.

This is the regressed submetric:
Event.Latency.ScrollUpdate.Touch.BrowserNotifiedToBeforeGpuSwap2

Note that  crbug.com/876753  is also about regressions on the same metrics on M70, but the regression ranges are different.

sadrul@ PTAL

Comment 2 by nzolghadr@chromium.org, Aug 28 

Issue 877478 has been merged into this issue.

Comment 3 by ssid@chromium.org, Sep 5 

This seems to be fixed in latest Dev.
https://uma.googleplex.com/p/chrome/timeline_v2?sid=7f7cb0005b839df8b01da929227526b2

The fix is not yet merged to beta. We can close this bug once the fix is merged.
[I have no pointers on what fixed this issue]

Comment 4 by sadrul@chromium.org, Sep 6

Status: Fixed (was: Assigned)
Fixed by crrev.com/586143 for  issue 867581  (and merged to 69 in crrev.com/c/1198745).
►

Sign in to add a comment