New issue
Advanced search Search tips

Issue 768861 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 768381
Owner: ----
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero regression in media.tough_video_cases at 503955:503956

Project Member Reported by johnchen@chromium.org, Sep 26 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 26 2017

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

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


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

win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 26 2017


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : dropped_frame_count/crowd1080.mp4


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.tough_video_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8967375905879270832


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 27 2017

Mergedinto: 768381
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Eric Seckler
  Commit : 1b697fc546af51e355c458bc4e10f821a1c8d551
  Date   : Sun Sep 24 07:41:53 2017
  Subject: [viz] Ensure that ClientLTFS acknowledges racy BeginFrames.

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : dropped_frame_count/crowd1080.mp4
  Change       : 1100.00% | 0.0714285714286 -> 0.888888888889

Revision             Result                     N
chromium@503950      0.0714286 +- 0.963624      14      good
chromium@503951      0.0714286 +- 0.963624      14      good
chromium@503952      0.666667 +- 1.41421        9       bad       <--
chromium@503953      1.0 +- 4.24264             21      bad
chromium@503955      1.28571 +- 2.9761          14      bad
chromium@503960      0.888889 +- 2.62467        9       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.tough_video_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8967374418737058480


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment