New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 599366 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

33.3% regression in v8.detached_context_age_in_gc at 384001:384058

Project Member Reported by mlippautz@chromium.org, Mar 31 2016

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiIaSpQoM


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

chromium-rel-win7-gpu-nvidia
This test seems far too noisy/bimodal to act on. How do we deal with these discrete values?
Cc: hpayer@chromium.org
hpayer, do we have an owner for this test? See my concerns in c#2.
hpayer@, ping. 
Labels: Needs-Feedback
Gentle remainder.
@hpayer -- Could you please respond to Comment# 3 and update the issue.
Thank You.
Status: WontFix (was: Assigned)
As discussed offline w/ hpayer@, the test depends on how much floating garbage is in the system. We'll keep the test because large spikes still point to memory leaks.

This one is noise though.

Sign in to add a comment