New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 793507 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Incorrect request timestamp on plznavigate document requests

Project Member Reported by paulir...@chromium.org, Dec 9 2017

Issue description

When throttling is on (in this case set to 3000ms of latency), the resulting trace doesn't *look* like latency is being applied, as the request is very short.

However, the time delay is being applied. It's just our timestamp instruemementation to get the start of the request is incorrect.


See screenshot.   First trace is with --disable-browser-side-navigation applied, second without.




 
throtted-example.com-noplznavigate-v-plznavigate.png
159 KB View Download
Cc: phulce@chromium.org
Status: WontFix (was: Assigned)
I believe this has been fixed once we started emitting network instrumentation events for navigation from the browser (http://crrev.com/536402). If this still reproduces, please reopen.

Sign in to add a comment