Closed Bug 1931514 Opened 2 months ago Closed 2 months ago

Make sure asyncOpenTime is not null

Categories

(Core :: Networking, defect, P2)

defect

Tracking

()

RESOLVED FIXED
134 Branch
Tracking Status
firefox134 --- fixed

People

(Reporter: valentin, Assigned: valentin)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(2 files)

Currently we set mAsyncOpenTime to 0 if timing isn't enabled for the channel.
For this bug we should consider not resetting the timestamp like here: https://hg.mozilla.org/try/rev/51ec9e60ae815fcfc5f2a2a845826ed7d68007f3
I'm not sure if nsITimedChannel::timingEnabled is still needed, so I'd consider removing it.

Timing should always be enabled.

Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/b725bc0904ff Make sure mAsycOpenTime is not null r=necko-reviewers,kershaw https://hg.mozilla.org/integration/autoland/rev/169255215767 Remove nsITimedChannel.timingEnabled r=necko-reviewers,kershaw
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: