Closed
Bug 1352174
Opened 8 years ago
Closed 8 years ago
Label the use of NS_New(In|Out)putStreamReadyEvent in ImageLib
Categories
(Core :: Graphics: ImageLib, defect, P3)
Core
Graphics: ImageLib
Tracking
()
RESOLVED
DUPLICATE
of bug 1372426
People
(Reporter: bevis, Assigned: aosmond)
References
Details
(Whiteboard: [gfx-noted])
This is a follow-up of bug 1335601 comment 3.
The frequency of nsInputStreamReadyEvent is high according to the telemetry report in bug 1333984.
This shall be label in priority.
|
Reporter | |
Comment 1•8 years ago
|
||
Note: NS_NewPipe also implicitly creates Pipe(In|Out)putStream.
When NS_New(In|Out)putStreamReadyEvent will be called when ::AsyncWait(..., nsIEventTarget* aTarget) is called.
So, we could provide a proper {DocGroup|System}Group versioned EventTarget to run these (In|Out)putStreamEvent runnables.
|
||
Comment 2•8 years ago
|
||
All of these are in image _encoders_, not decoders. So I don't expect these to come up very often at all. Not that they don't need to be done, just as far as prioritizing goes.
|
|
Reporter | |
Updated•8 years ago
|
Summary: Label the use of NS_New(In|Out)putStreamReadyEvent → Label the use of NS_New(In|Out)putStreamReadyEvent in ImageLib
Priority: -- → P3
Whiteboard: [gfx-noted]
|
Assignee | |
Updated•8 years ago
|
Assignee: nobody → aosmond
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 3•8 years ago
|
||
Hmm, on further investigation of the code (which I was not familiar with at all, hence why it was not obvious :)), I believe all we needed to do here got fixed as part of bug 1372426.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•