Closed
Bug 1598321
Opened 6 years ago
Closed 6 years ago
InputStreamShim::AsyncWait() and OutputStreamShim::AsyncWait() are not one-shot
Categories
(Core :: Networking: HTTP, defect, P1)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
mozilla73
| Tracking | Status | |
|---|---|---|
| firefox73 | --- | fixed |
People
(Reporter: michal, Assigned: michal)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
The implementation of nsIAsyncOutputStream and nsIAsyncInputStream doesn't comply with description in the IDL:
https://searchfox.org/mozilla-central/rev/652014ca1183c56bc5f04daf01af180d4e50a91c/xpcom/io/nsIAsyncOutputStream.idl#46
https://searchfox.org/mozilla-central/rev/652014ca1183c56bc5f04daf01af180d4e50a91c/xpcom/io/nsIAsyncInputStream.idl#46
|
Assignee | |
Comment 1•6 years ago
|
||
InputStreamShim and OutputStreamShim now hold a strong reference to the callback and it's released after calling nsIInputStreamCallback::OnInputStreamReady() and nsIOutputStreamCallback::OnOutputStreamReady()
|
||
Updated•6 years ago
|
Whiteboard: [necko-triaged]
Pushed by mnovotny@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9a8e9ac01476
InputStreamShim::AsyncWait() and OutputStreamShim::AsyncWait() are not one-shot, r=dragana
|
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox73:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla73
You need to log in
before you can comment on or make changes to this bug.
Description
•