New issue
Advanced search Search tips

Issue 806209 link

Starred by 1 user
Status: WontFix
Owner:
ofrobots@google.com
Closed: Jan 2018
Cc:
petermarshall@chromium.org
u...@chromium.org
ofrobots@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.5%-11.7% regression in system_health.memory_desktop at 531347:531477

Project Member Reported by petermarshall@chromium.org, Jan 26 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 26 2018 

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

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


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

chromium-rel-win7-dual
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 26 2018

Cc: ofrobots@google.com u...@chromium.org
Owner: ofrobots@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16fdd942840000

[heap] allocation step should before limit update
By ofrobots@google.com · Tue Jan 23 19:32:05 2018
v8 @ 95249bca1f473283c11b1a808e1a06767feeb899

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

Comment 4 by ofrobots@google.com, Jan 26 2018 

 Issue 806210  has been merged into this issue.

Comment 5 by ofrobots@google.com, Jan 29 2018 

 Issue 806208  has been merged into this issue.

Comment 6 by ofrobots@google.com, Jan 29 2018

Status: WontFix (was: Assigned)
The benchmarks seem sensitive to the precise timing of GC related events (e.g. idle scavenge). There isn't really anything actionable here.
►

Sign in to add a comment