New issue
Advanced search Search tips

Issue 641089 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

window.performance.timing values seem incorrect

Reported by sph...@gmail.com, Aug 25 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0

Steps to reproduce the problem:
1. Navigate to https://docs.google.com/document/d/14xhE4RtUOnqjXGR7JpOuEl2vMMWUPEu0iKrF3j1-iLI/edit
1.5 If the devtools are already open, close them.
2. Ctrl-R to reload and pay attention to how long it takes
3. Bring up the Console
4. Enter window.performance.timing.domComplete - window.performance.timing.navigationStart

What is the expected behavior?
The spinner displays for a couple of seconds, so I would expect a few thousand ms.

What went wrong?
Sometimes I get what seems to be about the right amount. Sometimes I get something much, much smaller. 9ms seems to be fairly common.

Did this work before? N/A 

Chrome version: 52.0.2743.116 (52.0.2743.116 (Official Build) (64-bit)Official Build) (64-bit)  Channel: stable
OS Version: Fedora 24
Flash Version: Shockwave Flash 11.2 r202

Here is the full timing object for an example where it gave me 1ms:

connectEnd:0
connectStart:0
domComplete:1472151998456
domContentLoadedEventEnd:1472151998456
domContentLoadedEventStart:1472151998456
domInteractive:1472151998456
domLoading:1472151998455
domainLookupEnd:0
domainLookupStart:0
fetchStart:0
loadEventEnd:1472151998456
loadEventStart:1472151998456
navigationStart:1472151998455
redirectEnd:0
redirectStart:0
requestStart:0
responseEnd:1472151998455
responseStart:0
secureConnectionStart:0
unloadEventEnd:0
unloadEventStart:0
 
Owner: caseq@chromium.org
Status: Assigned (was: Unconfirmed)
Andrey, could you please take a look?
Status: Archived (was: Assigned)
Bulk DevTools triage, closing low priority issues with no action plan.

Sign in to add a comment