[Webkit-unassigned] [Bug 184499] New: MotionMark gives wrong results after spectre mitigations of performance.now()

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=184499

            Bug ID: 184499
           Summary: MotionMark gives wrong results after spectre
                    mitigations of performance.now()
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: clopez at igalia.com
                CC: jonlee at apple.com, lforschler at apple.com,
                    rniwa at webkit.org

After spectre mitigations performance.now() not longer a hight resolution timer. This causes that the default settings of motionmark to give wrong results.

Motion mark supports 3 methods to measure performance as you can see here at the bottom right http://browserbench.org/MotionMark/developer.html

The default should be changed from performance.now() to one of the other methods.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180411/cc82219d/attachment-0002.html>