New issue
Advanced search Search tips

Issue 895366 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 15
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.2% regression in system_health.memory_desktop at 598784:598863

Project Member Reported by npm@chromium.org, Oct 15

Issue description

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

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


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

mac-10_13_laptop_high_end-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
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/17a95666e40000

Revert "Remove FlushForDriverCrashWorkaround" by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/e79108ef30139e7809fbada66cac635e39a23c7a
memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size: 1.97e+08 → 2.016e+08 (+4.668e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Status: WontFix (was: Assigned)
Dupe of 895401 and wontfix.

Sign in to add a comment