New issue
Advanced search Search tips

Issue 915066 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

3%-75% regression in system_health.memory_desktop at 616178:616220

Project Member Reported by benhenry@google.com, Dec 14

Issue description

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

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


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

linux-perf
mac-10_13_laptop_high_end-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: chrome-release-bot@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11cb7b6c140000

Updating trunk VERSION from 3639.0 to 3640.0 by chrome-release-bot@chromium.org
https://chromium.googlesource.com/chromium/src/+/e41ec3280a373f760d83347667a1c5c056cfdd5c
console:error:all: 4 → 7.1 (+3.1)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner

Sign in to add a comment