New issue
Advanced search Search tips

Issue 817691 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 644540
issue 773591



Sign in to add a comment

[meta] GetResourceLoadTiming() can be null

Project Member Reported by npm@chromium.org, Mar 1 2018

Issue description

Performance::GenerateResourceTiming calls GetResourceLoadTiming() and often assumes that the output is not null. But it seems that this can return null. We should investigate why this is happening and either returning null is a bug and must be fixed, OR returning null is reasonable and the code must always be surrounded with if statements when the output 
from GetResourceLoadTiming() is used.
 

Comment 1 by npm@chromium.org, Mar 1 2018

Cc: tyoshino@chromium.org
 Issue 803913  has been merged into this issue.

Comment 2 by npm@chromium.org, Mar 1 2018

Description: Show this description
Blockedon: 773591 644540
Cc: -tyoshino@chromium.org toyoshim@chromium.org ksakamoto@chromium.org yhirano@chromium.org
Summary: [meta] GetResourceLoadTiming() can be null (was: GetResourceLoadTiming() can be null)
CC-ing a few more people who may potentially be able to look at them as I'm hearing that this area's temporarily so understaffed that no one has enough bandwidth working on this one.

Individual bugs are: issue 773591, issue 644540

Comment 4 by npm@chromium.org, Jun 27 2018

Labels: -Pri-2 Pri-3
For now this bug does not seem to affect much so lowering priority.
npm@, any idea when you might be able to take a look at this? This popped up on the CSM triage rotation.
I think no one has had time to dig into this yet.

Sign in to add a comment