New issue
Advanced search Search tips

Issue 839752 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

54% regression in system_health.common_desktop at 555321:555366

Project Member Reported by hjd@google.com, May 4 2018

Issue description

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

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


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

chromium-rel-mac11-air
Cc: sdy@chromium.org ccameron@chromium.org
Owner: ccameron@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14e082abc40000

RemoteRWHVMac: Pass display parameters through NSViewBridge interface by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/3d6703376c34aa8915bc39ad86163cbb3dccd34f

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
This regressed significantly in  issue 835853 , then went down in my r552954, and this brings it back to the original level.

Sign in to add a comment