[Webkit-unassigned] [Bug 188620] New: Navigation Timing API reporting below 0 for response time (responseEnd - responseStart)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Aug 15 14:16:33 PDT 2018


            Bug ID: 188620
           Summary: Navigation Timing API reporting below 0 for response
                    time (responseEnd - responseStart)
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: iPhone / iPad
                OS: iOS 11
            Status: NEW
          Severity: Major
          Priority: P2
         Component: WebCore Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: msartintarm at gmail.com

I work on a site with millions of hits per day. We collect latency data and make assertions on the results client-side before using them in aggregate metrics.

We are receiving invalid metrics from the Safari browser for various iPhone / iPad devices using iOS 10 and 11.

The following interval is showing up as below 0 in many instances:

`performance.timing.responseEnd - performance.timing.responseStart`

In some cases the number is significantly below 0. It doesn't seem like it would ever make sense for this number to be below 0.

We collect samples of performance.timing data for which these errors occur. Here is a sample where responseEnd - responseStart is -28412:


        sub_family: "AppleWebKit"
        platform: "iPad"
        device: "iPad"
        os: "CPU OS 10_3_3 like Mac OS X"
        browser: "Safari"
        browser_version: "10.0"
        browser_engine_version: "603.3.8"

Let me know if there is any additional analysis / info I can attach that would be helpful.

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/20180815/cbb9584d/attachment.html>

More information about the webkit-unassigned mailing list