New issue
Advanced search Search tips

Issue 810500 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 14
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

24.4% regression in blink_perf.bindings at 534433:534535

Project Member Reported by chiniforooshan@chromium.org, Feb 8 2018

Issue description

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

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


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

chromium-rel-win7-dual
Cc: yangguo@chromium.org jkummerow@chromium.org
Owner: yangguo@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13c69aa9840000

Fix undefined behavior wrt float-cast-overflow in conversions-inl.h. by yangguo@chromium.org
v8 @ 0391a8c5aeeec96cf7a46e51c07328e37cd8b3c6

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
yangguo@, any updates?
Status: WontFix (was: Assigned)
I think this is a won't fix since it's a fix for a potential correctness issue. In addition to that, the fact that the benchmark regresses this much on such a local change indicated that it's a very narrow Microbenchmarks.

Sign in to add a comment