Issue metadata
Sign in to add a comment
|
First requests can have a negative started at time
Reported by
ville.la...@luotta.fi,
Feb 28 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: 1. Open DevTools 2. Browse to https://www.google.com 3. Check the first request timings What is the expected behavior? Queued at: 0 Started at: 0 What went wrong? Started at value is a negative number with a unit of µs. Did this work before? N/A Chrome version: 64.0.3282.186 Channel: stable OS Version: OS X 10.13.3 Flash Version:
,
Mar 1 2018
Able to reproduce this issue on reported version 64.0.3282.186 using Windows 10, Mac 10.13.3 and Ubuntu 14.04 with steps mentioned in comment#0. But issue is not reproducible on latest canary 66.0.3357.0. Hence providing reverse bisect info. Last Bad Build: 66.0.3346.0 First Good Build: 66.0.3347.0 CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/da651de72deefafe29d81c522234a2557475cc2b..30f8822a37972aabd4b76d4559d1062d6799c9cb Probably fixed by https://chromium-review.googlesource.com/912400 @ caseq: Please merge this to M-64 and M-65 if it is safe. Adding RB-Stable for M-64. Please change if not the case. Thanks!
,
Mar 1 2018
We won't merge it to either beta or stable, the severity of the bug doesn't justify the risk in my view. Note this is a large change and there were a few followups to fix the issues that resulted from it. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Mar 1 2018