New issue
Advanced search Search tips

Issue 638005 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 638006
Owner:
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

36.2% regression in memory.long_running_idle_gmail_background_tbmv2 at 411586:411607

Project Member Reported by benjhayden@chromium.org, Aug 15 2016

Issue description

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 16 2016

Mergedinto: 638006
Status: Duplicate (was: Assigned)

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Fix wrong state of IsolateInBackgroundNotification and IsolateInForegroundNotification.
Author  : hpayer
Commit description:
  
BUG= chromium:636368 , chromium:635965 , chromium:634900 

Review-Url: https://codereview.chromium.org/2245483004
Cr-Commit-Position: refs/heads/master@{#38598}
Commit  : b992a8e1899091e3c180a050c1a63fa1e29886d5
Date    : Fri Aug 12 08:13:56 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev    N  Good?
chromium@411585                0.857727  0.0218269  5  good
chromium@411591                0.828233  0.10376    5  good
chromium@411592                0.778226  0.0902132  5  good
chromium@411592,v8@64658b6c28  0.828513  0.0754609  8  good
chromium@411592,v8@e6e32315cc  0.797433  0.123227   8  good
chromium@411592,v8@b992a8e189  1.07464   0.151882   5  bad    <--
chromium@411593                1.03831   0.0548909  5  bad
chromium@411594                1.16801   0.195995   5  bad
chromium@411596                1.15151   0.148249   5  bad
chromium@411607                1.10675   0.0587761  5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 638005

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2
Test Metric: v8-gc-total_avg/v8-gc-total_avg
Relative Change: 29.03%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1805
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004219925709244000


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5903887978987520

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Sign in to add a comment