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

Issue 622218 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
please use my google.com address
Closed: Jul 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.4% regression in blink_perf.canvas at 401071:401092

Project Member Reported by toyoshim@chromium.org, Jun 22 2016

Issue description

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

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


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

chromium-rel-mac-retina
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Jun 22 2016

Cc: roc...@chromium.org
Owner: roc...@chromium.org

=== Auto-CCing suspected CL author rockot@chromium.org ===

Hi rockot@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Implements Mojo-based waiting for IPC::SyncChannel
Author  : rockot
Commit description:
  
Changes SyncChannel et al to use Mojo message pipe handles
and mojo::SyncHandleRegistry for sync waiting in lieu of
base::WaitableEvent.

This is necessary to support sync Mojo interface messages
without risk of deadlock.

BUG=612500

Review-Url: https://codereview.chromium.org/2072393003
Cr-Commit-Position: refs/heads/master@{#401090}
Commit  : 64e65de0553abe1c870978ec4dee77da14d93d9e
Date    : Tue Jun 21 20:20:53 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@401070  167.584  2.4275   5  good
chromium@401081  162.469  2.63111  5  good
chromium@401087  157.589  3.56916  5  good
chromium@401089  159.211  4.17278  5  good
chromium@401090  137.82   5.56644  5  bad    <--
chromium@401092  139.519  4.50406  5  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 622218

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: getImageData/getImageData
Relative Change: 16.75%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1351
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009167476525444096


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

| 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!
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 3 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Assigned)
This has recovered.

Sign in to add a comment