New issue
Advanced search Search tips

Issue 895272 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
npm@chromium.org
vasi...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

54.6% regression in rendering.desktop/thread_raster_cpu_time_per_frame at 598784:598863

Project Member Reported by npm@chromium.org, Oct 15 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 15 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=895272

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=ada94b7595aa3b5d17e76af38dbededb4151aa19276b97452811acb19647b599


Bot(s) for this bug's original alert(s):

mac-10_13_laptop_high_end-perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 15 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14fb1782e40000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Oct 15

Cc: vasi...@chromium.org
Owner: vasi...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12cf647ce40000

Revert "Update GetAccessibleName() in view::ImageView and view::Button" by vasilii@chromium.org
https://chromium.googlesource.com/chromium/src/+/03cb5c6ae11ab562bc364560972f74efdd66a761
thread_raster_cpu_time_per_frame: No values → 0.0436

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 6 by vasi...@chromium.org, Oct 15

Owner: ----
Status: Available (was: Assigned)
I reverted the CL as a sheriff. There is an attempt to land it again https://chromium-review.googlesource.com/c/chromium/src/+/1278076

It looks simple enough so I don't think it caused anything.

Comment 8 by npm@chromium.org, Oct 15 

Trying bisect again.
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Oct 15

Owner: vasi...@chromium.org
Status: Assigned (was: Available)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1497e12ee40000

Revert "Update GetAccessibleName() in view::ImageView and view::Button" by vasilii@chromium.org
https://chromium.googlesource.com/chromium/src/+/03cb5c6ae11ab562bc364560972f74efdd66a761
thread_raster_cpu_time_per_frame: No values → 0.04429

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 10 by vasi...@chromium.org, Oct 16

Owner: ----
Status: Available (was: Assigned)
Will be fixed by reland https://chromium-review.googlesource.com/c/chromium/src/+/1278076
►

Sign in to add a comment