New issue
Advanced search Search tips

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

2.2%-75% regression in console:error:all,memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size at 615406:615452

Project Member Reported by 42576172...@developer.gserviceaccount.com, Dec 12

Issue description

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

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


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

mac-10_12_laptop_low_end-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/15efb99c140000

Updating trunk VERSION from 3637.0 to 3638.0 by chrome-release-bot@chromium.org
https://chromium.googlesource.com/chromium/src/+/7688eb868aa9659a24979efc6bffd551f20080a3
console:error:all: 4 → 7.3 (+3.3)

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