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

Issue 309570 link

Starred by 7 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Oct 2013
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Network tab shows incorrect timings

Reported by vishwana...@gmail.com, Oct 21 2013

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1676.2 Safari/537.36

Steps to reproduce the problem:
Not sure how to reproduce. While working on the internal application found following. Application URL can not be shared.

What is the expected behavior?
Timings should be shown properly.

What went wrong?
Timing for some resource is calculated as in no of days so the overall report also shows incorrect values.
Check attached files for more info.

Did this work before? Yes Works good in Chrome 30.

Chrome version: 32.0.1676.2  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 11.9 r900
 
Chrome_Networkpanel_bug.png
31.6 KB View Download
Chrome_Networkpanel_bug_2.png
23.5 KB View Download
Cc: ashej...@chromium.org
 Issue 309571  has been merged into this issue.
 Issue 309572  has been merged into this issue.

Comment 3 by mmenke@chromium.org, Oct 21 2013

Cc: mmenke@chromium.org
Labels: Cr-Internals-Network
That looks an awful lot like the number of days since January 1, 1970.  Maybe we're misinterpreting a time as a delta somewhere.
Cc: eustas@chromium.org
I also have the same issue, with Chrome Canary (Version 32.0.1677.0 canary) on Mac OS X.

It occurs only when testing locally and loading LESS or HTML files with JavaScript. I also use a custom web server built in NodeJS so this might be the cause. I'll try to recreate a small code as I cannot give you what I have at work.
Cc: msrchandra@chromium.org
@vishwanatharondekar:
Could you please provide us with any sample URL for verifying the issue.
Thanks in Advance.

Comment 7 by eustas@chromium.org, Oct 24 2013

Cc: -eustas@chromium.org
Owner: eustas@chromium.org
Trying to find what triggers it, so that I can replicate it somewhere else.

Comment 9 Deleted

Looks like dupe of  Issue 230886 .

At least repro scenario works.
Analysis: ResourceLoader::requestSynchronously() reports finish time as "wall time" whereas "monotonic" time is expected.


Repro URL: http://www.webpagetest.org/
Project Member

Comment 13 by bugdroid1@chromium.org, Oct 29 2013

The following revision refers to this bug:
    http://src.chromium.org/viewvc/blink?view=rev&rev=160817

------------------------------------------------------------------------
r160817 | eustas@chromium.org | 2013-10-29T09:44:12.957337Z

Changed paths:
   M http://src.chromium.org/viewvc/blink/trunk/Source/core/fetch/ResourceLoader.cpp?r1=160817&r2=160816&pathrev=160817

Use monotonic finish time for sync request completion.

Currently wall time is used. That is wrong.

Since request is performed synchronously, current time fits well as
finish time.

BUG= 309570 

Review URL: https://codereview.chromium.org/47603003
------------------------------------------------------------------------
Status: Fixed
Labels: -Via-Wizard -Type-Bug -OS-Windows Merge-Requested Type-Bug-Regression M-31
Cc: agautam@chromium.org
 Issue 319705  has been merged into this issue.
Labels: -Merge-Requested Merge-Approved
Project Member

Comment 18 by bugdroid1@chromium.org, Dec 3 2013

Labels: -Merge-Approved merge-merged-1650
The following revision refers to this bug:
    http://src.chromium.org/viewvc/blink?view=rev&rev=163068

------------------------------------------------------------------------
r163068 | eustas@chromium.org | 2013-12-03T07:47:40.875538Z

Changed paths:
   M http://src.chromium.org/viewvc/blink/branches/chromium/1650/Source/core/fetch/ResourceLoader.cpp?r1=163068&r2=163067&pathrev=163068

Merge 160817 "Use monotonic finish time for sync request complet..."

> Use monotonic finish time for sync request completion.
> 
> Currently wall time is used. That is wrong.
> 
> Since request is performed synchronously, current time fits well as
> finish time.
> 
> BUG= 309570 
> 
> Review URL: https://codereview.chromium.org/47603003

TBR=eustas@chromium.org

Review URL: https://codereview.chromium.org/101293002
------------------------------------------------------------------------

Sign in to add a comment