avoid reinitializing the timers in HTTP3
Categories
(Core :: Networking: HTTP, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox82 | --- | fixed |
People
(Reporter: CuveeHsu, Assigned: jhsu)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
Reporter | ||
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Will this be fixed by bug 1646024?
Reporter | ||
Comment 2•3 years ago
|
||
Thanks for referring to this.
I've been patched bug 1646024 and I still saw several SetupTimer from Read or Write before the previous one is fired.
Reporter | ||
Comment 3•3 years ago
|
||
I had a patch and will post it later. It will ease the implementation of the timer probe in bug 1655566
Reporter | ||
Comment 4•3 years ago
|
||
We might overwrite the timer accenditally. Raise the severity.
Reporter | ||
Comment 5•3 years ago
|
||
SetupTimer
came from [Read|Write]SegmentsAgain
and could be set before the previous one fire.
Therefore, it will accenditally remove the previous one and set the new timeout by current timer implementation.
If we set a long timeout, the previous timer could be wrongly removed.
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Comment 6•3 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:CuveeHsu, could you have a look please?
For more information, please visit auto_nag documentation.
Pushed by ddamjanovic@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/40bdd210fd2f avoid reinitializing the timers for ProcessOutputAndEvents, r=dragana,necko-reviewers
Comment 8•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Description
•