Closed
Bug 1655895
Opened 5 years ago
Closed 4 years ago
bogus timeout passed to Http3Session::SetupTimer
Categories
(Core :: Networking: HTTP, defect, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
82 Branch
Tracking | Status | |
---|---|---|
firefox82 | --- | fixed |
People
(Reporter: CuveeHsu, Assigned: jhsu)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
I often see the bogus log
Http3Session::SetupTimer to 18446744073709551615 ms
Here's the culprit:
Output::None passed uint::max to indicated a no-op.
We should not set a timer with uint64::max as a delay which hurts performance
Reporter | ||
Comment 1•5 years ago
|
||
Depends on D85233
Reporter | ||
Updated•5 years ago
|
Assignee: CuveeHsu → nobody
Comment 2•4 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.
Flags: needinfo?(CuveeHsu)
Pushed by ddamjanovic@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0f723de1af73
do not set a timer for neqo passed a UINT64::MAX, r=dragana,necko-reviewers
Updated•4 years ago
|
Assignee: nobody → jhsu
Status: NEW → ASSIGNED
Comment 4•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•