New issue
Advanced search Search tips

Issue 845654 link

Starred by 3 users
Status: Available
Owner: ----
Cc:
sunyunjia@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 853106



Sign in to add a comment

1%-32.8% regression in blink_perf.layout at 557293:557695

Project Member Reported by sunyunjia@chromium.org, May 22 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 22 2018 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=845654

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


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

android-one
chromium-rel-mac11-air
chromium-rel-mac12
linux-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 27 2018

Cc: mlippautz@chromium.org
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14b9a0c2240000

[oilpan] Enable incremental marking buildflag by mlippautz@chromium.org
https://chromium.googlesource.com/chromium/src/+/838fb3bd2db6a2869a0efc6e7e3154f954f74b70

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

Comment 4 by mlippautz@chromium.org, Nov 30

Blocking: 853106
Cc: -mlippautz@chromium.org
Components: Blink>MemoryAllocator>GarbageCollection
Owner: ----
Status: Available (was: Assigned)
Will be swallowed for now. Blocking on the bug that collects write barrier regressions.
►

Sign in to add a comment