Issue metadata
Sign in to add a comment
|
2% regression in smoothness.tough_scrolling_cases at 558208:558310 |
||||||||||||||||||||||
Issue descriptionmean_pixels_checkerboarded regressed by ~2% on Nexus 5: https://chromeperf.appspot.com/report?sid=8207bc3e5f1bcf5128baf7e64bf8b857005049e14707bbface31f4999289710d Kicking off a bisect.
,
May 23 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12d4bbec240000 Fix Regression: Black patch is seen while opening new page by yiyix@chromium.org https://chromium.googlesource.com/chromium/src/+/6a4ede3e8b19101ba5b1735e0a2178b9541a21a3 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
May 23 2018
There's also a regression in UMA in Compositing.RenderPass.AppendQuadData.CheckerboardedNeedRasterContentArea in Android Canary around the same time period.
,
May 23 2018
yiyix@ is OOO right now, cc'ing fsamuel@ for probably knowing best of what happened in that CL.
,
May 24 2018
this bug is fixed in this patch: https://chromium-review.googlesource.com/c/chromium/src/+/1067147 Could you let me know if it is still an issue? Thank you.
,
May 24 2018
Please verify and confirm as soon as possible
,
May 24 2018
It looks like performance improved with the fix in #5, but there might have been a second regression in the meanwhile (from some other CL). I'll open another bug to bisect that.
,
May 24 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-67; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-67 label, otherwise remove Merge-TBD label. Thanks.
,
May 24 2018
The regression happened in M67 and the fix landed in M68, so this does need a merge. yiyix@, please make sure this gets merged either on this bug or on one of the other bugs associated with the CL from #5.
,
May 25 2018
The problematic cl, Fix Regression: Black patch is seen while opening new page, is landed on May 14th and the branch cut date for M67 is April 12th. Could you double check if this regression happened in M67? If that is the case, other cl may have cause the regression.
,
May 25 2018
I'm so sorry, I somehow misread the branch date calendar and thought May 14 was still during M67!
,
May 25 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-68; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-68 label, otherwise remove Merge-TBD label. Thanks.
,
May 25 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, May 22 2018