New issue
Advanced search Search tips

Issue 873559 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.3% regression in speedometer2 at 580870:580899

Project Member Reported by jarin@google.com, Aug 13

Issue description

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

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


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

Android Nexus6 WebView Perf
Cc: mlippautz@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13fc4ad0e40000

[bindings,heap] Prepare PerIsolateData for holding different heap tracer by mlippautz@chromium.org
https://chromium.googlesource.com/chromium/src/+/1186c664d583e43a45f365d4a5291bed032542bd
5549 → 5958 (+409.4)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None
Cc: -mlippautz@chromium.org
Owner: mlippautz@chromium.org
Michi, could you take a look, please?
Issue 873560 has been merged into this issue.
Status: Fixed (was: Assigned)
That CL was reverted and never relanded. We took a different approach were we keep two different class hierarchies separate instead of using a virtual interface as common base.

https://chromium-review.googlesource.com/c/chromium/src/+/1170743

Sign in to add a comment