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

[bugzilla-daemon at webkit.org]

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

Carlos Alberto Lopez Perez <clopez at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---
(In reply to Simon Fraser (smfr) from comment #1)
> perf.now() and rAF timestamp should be quantized the same way, and I think
> Date.now() will also be.

That makes sense, actually.

I have been testing motionmark with WPE trunk and I have been getting sometimes some weird results with the default settings (like 1 points on some tests with a +-3000% percent of variance).

So, at first I thought it could be related to the spectre mitigations of performance.now() because I couldn't reproduce with the other methods of the benchmark like rAF.

But I'm not able to reproduce this with a webkit build of last trunk on Mac. So it should be something else...

I'm closing this as invalid, then.

Thanks for the comments.

-- 
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/b11b6fd0/attachment-0002.html>