New issue
Advanced search Search tips

Issue 911567 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 5
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1%-1.7% regression in memory.desktop at 612368:612505

Project Member Reported by toyoshim@chromium.org, Dec 4

Issue description

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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

memory.desktop - Benchmark documentation link:
  None
Cc: 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/142edf42140000

OOP-R: GrContext::flush and glFlush at every DoEndRasterCHROMIUM by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/193f427a339c3e2016996c0018d55fa631b8dbf1
memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size: 1.262e+08 → 1.287e+08 (+2.499e+06)

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

Benchmark documentation link:
  None
Status: WontFix (was: Assigned)
Marking WontFix.

Sign in to add a comment