New issue
Advanced search Search tips

Issue 827975 link

Starred by 1 user
Status: WontFix
Owner:
adamk@chromium.org
Closed: Apr 2018
Cc:
gsat...@chromium.org
adamk@chromium.org
u...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.7%-5.9% regression in system_health.memory_mobile at 545918:546040

Project Member Reported by ulan@google.com, Apr 2 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 2 2018 

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

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


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

android-nexus5X
chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 2 2018

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

Revert "Reland "[parser] Remove pretenuring of closures assigned to properties"" by adamk@chromium.org
https://chromium.googlesource.com/v8/v8/+/5cf2ae5a4d7224198a0474eb27cc618b6843bc32

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

Comment 4 by adamk@chromium.org, Apr 2 2018

Status: WontFix (was: Assigned)
This is a revert of a recent change, no action to be taken.
►

Sign in to add a comment