We generate HAR timing and HAR has a hard requirement for things to come in a specific order (block -> connect -> send -> receive). When analyzing the timing info that netstack gives us (LoadTimingInfo), quic sometimes shows that it has sent out the request before it finished connecting to the site.

I gave a first glance at it and it appears that the reason is because it hops threads after crypto connection was established and then records the time.

A repo case that I am using right now is the ad_status.js file on http://paulirish.com/

This is not blocking us, but we do have some nasty code hacks to work around this.