[meta] GetResourceLoadTiming() can be null |
||||
Issue descriptionPerformance::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.
,
Mar 1 2018
,
Mar 2 2018
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
,
Jun 27 2018
For now this bug does not seem to affect much so lowering priority.
,
Oct 16
npm@, any idea when you might be able to take a look at this? This popped up on the CSM triage rotation.
,
Oct 16
I think no one has had time to dig into this yet. |
||||
►
Sign in to add a comment |
||||
Comment 1 by npm@chromium.org
, Mar 1 2018