New issue
Advanced search Search tips

Issue 871402 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.1% regression in rendering.desktop at 578682:578865

Project Member Reported by chiniforooshan@chromium.org, Aug 6

Issue description

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

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


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

mac-10_13_laptop_high_end-perf
Cc: uwyiming@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1589801c640000

Remove queuing the DidCommitAndDrawCompositorFrame message. by uwyiming@google.com
https://chromium.googlesource.com/chromium/src/+/f0d7951f253c73c2678c83af541481bb34276a40
0.03652 → 0.04033 (+0.003811)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner

Sign in to add a comment