Closed
Bug 1881490
Opened 3 months ago
Closed 3 months ago
Avoid duplicate process_output calls
Categories
(Core :: Networking: HTTP, task, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
125 Branch
| Tracking | Status | |
|---|---|---|
| firefox125 | --- | fixed |
People
(Reporter: kershaw, Assigned: kershaw)
Details
(Whiteboard: [necko-triaged] [necko-priority-queue])
Attachments
(1 file)
neqo could produce multiple DataWritable events and for each stream, we insert the duplicate stream into the write queue and dispatch a ResumeSend runnable. Since the tx queue should be empty after the first ResumeSend runnable completed, executing the reset ResumeSend runnables is a waste of resource.
|
Assignee | |
Comment 1•3 months ago
|
||
Pushed by kjang@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/cd0f12ca6424 Don't insert the same stream into TX queue, r=necko-reviewers,jesup
|
||
Comment 3•3 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 months ago
status-firefox125:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 125 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•