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

Issue 761681 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
█ sc00335...@techmahindra.com
jmukthavaram@chromium.org
panicker@chromium.org
yoavweiss@chromium.org
npm@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

resource timing api giving PerformanceEntry for an ongoing fetch stream

Reported by bryanshe...@gmail.com, Sep 3 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce the problem:

1. start a stream using fetch API
2. call performance.getEntries() before the stream is done
3. the url requested by fetch API is not found in performance entries

https://jsfiddle.net/kzg92wsr/4/

What is the expected behavior?

What went wrong?
I wonder if we can have a performance entry for the ongoing stream, so that we can measure network during a long stream

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 60.0.3112.113  Channel: stable
OS Version: OS X 10.12.6
Flash Version:

Comment 1 by sc00335...@techmahindra.com, Sep 4 2017

Cc: sc00335...@techmahindra.com
Labels: Needs-Triage-M60 Needs-Feedback Triaged-ET
Tested this issue on 60.0.3112.113 on Mac 10.12.6 . By opening the provided test case file observing less memory usage from chrome task manager[Memory:222 MB and CPU usage is 5.0]

@ bryanshen005: Could you please let us know from where we can check the performance issue? Attaching screenshot of dev console error. Please take a look and let me know is this the issue you are saying.

NOTE:The console error is observed on Firefox browser as well.
Issue_761681.png
213 KB View Download

Comment 2 by bryanshe...@gmail.com, Sep 5 2017 

Hi there, 

The report is not about the performance. It's about the PerformanceResourceTimingEntry. From the first two logs, the entry for the fetched url cannot be found. The fetched url can only be found in the last two logs when the fetch stream has been finished.
Screen Shot 2017-09-04 at 9.05.53 PM.png
340 KB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 5 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by jmukthavaram@chromium.org, Sep 5 2017

Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback
bryanshen005@,

Thanks for the reply.
Tested the issue as per C#0 & C#2 on Mac 10.12.6 & Windows 7 using chrome reported version#60.0.3112.113(Stable) & Canary#63.0.3205.0.

Steps followed:
--------------
1. Launched chrome
2. Navigate to https://jsfiddle.net/kzg92wsr/4/ fiddle
3. Open dev tools & navigate to 'Console' section
4. Run the fiddle once & observe console errors
5. Checked all the PerformanceResourceTimingEntries of console errors

Observation:
------------
Not found any fetched URL entries.

Please find the attached screencast & let us know the clear expected result & revert us if we miss any steps to reproduce the issue.

Thanks..!!
761681.mp4
4.4 MB View Download

Comment 5 by ricea@chromium.org, Sep 5 2017

Labels: -Needs-Feedback -Needs-Triage-M60
Status: WontFix (was: Unconfirmed)
This is working as intended. The PerformanceEntry is not added until the request is complete. See the standard text at https://www.w3.org/TR/resource-timing-2/#processing-model, particularly step 21.

You could try filing an issue against the standard at https://github.com/w3c/resource-timing/issues, but I suspect that there were carefully considered reasons for doing it this way.
►

Sign in to add a comment