Closed
Bug 1761548
Opened 2 years ago
Closed 2 years ago
Add basic locking to nsStorageStream
Categories
(Core :: XPCOM, enhancement)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
100 Branch
Tracking | Status | |
---|---|---|
firefox100 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
Details
Attachments
(1 file)
This should make it slightly safer to to try to read from a nsStorageInputStream while the stream is being concurrently written to on another thread, though it will still not behave very well as there is no nsIAsyncInputStream support.
Individual input streams are still non-threadsafe with this change.
Assignee | ||
Comment 1•2 years ago
|
||
This should make it slightly safer to to try to read from a
nsStorageInputStream while the stream is being concurrently written to
on another thread, though it will still not behave very well as there is
no nsIAsyncInputStream support.
Individual input streams are still non-threadsafe with this change.
Pushed by nlayzell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/af7b7e28d468 Add basic locking to nsStorageStream, r=xpcom-reviewers,mccr8
Comment 3•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox100:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•