Use a different way to determine the end of the upload stream in Http3tream
Categories
(Core :: Networking: HTTP, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox98 | --- | fixed |
People
(Reporter: dragana, Assigned: dragana)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files)
Assignee | ||
Comment 1•4 years ago
|
||
This is similar to the nsHttpConnection approach.
Assignee | ||
Comment 2•4 years ago
|
||
The patch adds a diagnostic assertion into Http3SStream code.
Comment 4•4 years ago
|
||
bugherder |
Comment 6•4 years ago
|
||
bugherder |
Comment 7•4 years ago
|
||
There is one crash because of the added assertion:
https://crash-stats.mozilla.org/report/index/893af824-7907-44bd-9917-6a9d60220128
![]() |
||
Comment 9•4 years ago
|
||
Should the crash reports from the assertion (see comment 7) get a new bug? There are 13 crashes from 7+ devices.
Assignee | ||
Comment 10•4 years ago
|
||
(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #9)
Should the crash reports from the assertion (see comment 7) get a new bug? There are 13 crashes from 7+ devices.
I will open another bug. The assertion is a sign that something is not using necko API correctly or, unlikely, the check is wrong. The second is unlikely because I would expect more failures in that case.
Assignee | ||
Comment 11•4 years ago
|
||
I moved the crash to bug 1753002.
Description
•