New issue
Advanced search Search tips

Issue 827996 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 13
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.6%-11.1% regression in system_health.memory_mobile at 545911:546033

Project Member Reported by ulan@google.com, Apr 2 2018

Issue description

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

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


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

android-nexus5
android-nexus5X
chromium-rel-mac11-pro
linux-release
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/17476247440000

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
Status: WontFix (was: Assigned)
This was a revert, not actionable.

Sign in to add a comment