Issue metadata
Sign in to add a comment
|
DevTools: stalled time is incorrect
Reported by
david.sm...@googlemail.com,
Nov 6 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36 Steps to reproduce the problem: 1. Make request to endpoint (I'm using webpack dev server and node) 2. Record the xhr request in dev tools 3. Every other request is different and the total isn't even close to the combined numbers What is the expected behavior? It reports the correct timings. What went wrong? Hitting the same endpoint seems to create a strange issue. The individual timings suggest they are correct but the total isn't. Did this work before? Yes Chrome version: 62.0.3202.75 Channel: stable OS Version: OS X 10.13.1 Flash Version: Sorry can't remember the version number when it last worked.
,
Nov 6 2017
,
Nov 7 2017
Good morning, I've tried in vain to reproduce this error using a public API and codepen but unfortunately I'm unable to reproduce. I can't give you access to the sensitive data available at that endpoint for obvious reasons. There are also security measures in place to stop external access anyway. I can tell you it's using node/express, webpack dev server and React but I can't recreate the exact ecosystem using codepen or the like as I'm using various packages, like request and bluebird. This pen is in essence what I'm doing (without Redux). https://codepen.io/anon/pen/BmLpeW Sorry I can't be more of a help. I can see from other browser timings and using the individual figures that there isn't a problem with the actual request, just the total in DevTools. Regards, Dave.
,
Nov 7 2017
Unable to reproduce this issue on reported version 62.0.3202.75 using Mac 10.12.6 with steps mentioned below. 1.Launched chrome and navigated to https://codepen.io/anon/pen/BmLpeW 2.Opened devtools > Network tab 3.Clicked on "Make Request" and observed below data on network tab. Attaching screenshot for reference. @Reporter: Could you please check the screenshot and let us know the expected behaviour. This would help in further triaging of the issue
,
Dec 1 2017
,
Dec 1 2017
Hi, as previously mentioned, I can't allow you access to the endpoints I'm using and I can't reproduce the error without completely recreating the technology stack currently being used. I can see by your screenshot that the timings for the request in the overlay all add up to the total at the bottom of the overlay. For reasons unknown, you can see in my earlier screenshots, the total was incorrect. I've checked in other browsers and they appear to be reporting the correct time, which would suggest the underlying code is valid. Sorry, but I don't have the time to completely recreate an enterprise level web application to resolve an issue other people aren't seeing. My apologies I can't be of anymore help.
,
Dec 14 2017
,
Oct 12
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Nov 6 2017