New issue
Advanced search Search tips

Issue 752526 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

51.5% regression in v8.browsing_mobile at 489459:489543

Project Member Reported by ulan@google.com, Aug 4 2017

Issue description

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

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


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

android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 14 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-total_max/browse_shopping/browse_shopping_lazada

Revision             Result                  N
chromium@489458      40.7669 +- 13.6648      21      good
chromium@489543      41.081 +- 10.5088       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.shopping.lazada v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by u...@chromium.org, Aug 21 2017

Status: WontFix (was: Assigned)
Not reproducible.

Sign in to add a comment