New issue
Advanced search Search tips

Issue 872678 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 872582
Owner:
Closed: Aug 14
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

39.1% regression in rendering.desktop at 581341:581356

Project Member Reported by toyoshim@chromium.org, Aug 9

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=872678

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


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

mac-10_13_laptop_high_end-perf
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12b4f18c640000
In the bisect, the first bad revision shows a good result.
I'd start another bisect for a later revision range that contains the worst point.
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/169bb5c2640000
r581340 good
r581356 good
r581488 bad
r581494 bad

Sp, will run another bisect between r581356 and r581488
Cc: pdr@chromium.org
Owner: pdr@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16be60a8640000

Remove lifecycle updates for preferred content size changes by pdr@chromium.org
https://chromium.googlesource.com/chromium/src/+/601fd07dc26269d097d6ef6bd90f1203d361a72c
49.39 → 56.08 (+6.692)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 872582
Status: Duplicate (was: Assigned)

Sign in to add a comment