Closed
Bug 240131
Opened 20 years ago
Closed 12 years ago
NPStream's necko stream ownership and handling seems shady.
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla15
People
(Reporter: jst, Assigned: jaas)
Details
Attachments
(1 file)
4.74 KB,
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
Seems like _destroystream() (in ns4xPlugin.cpp) should do more cleaning up of the underlying necko streams than it does, like, closing it etc. And the ownership of the underlying stream is far from obvious, and should be clarified in the code.
Updated•15 years ago
|
QA Contact: plugins
From related code comments the primary concern seems to be what we store for stream ndata. I'm working on that code now, taking this.
I didn't find any problems during my review of stream cleanup, but there are some things that can be more clear. This patch is largely improving comments, but it also does a little bit of re-organization and makes owning references more clear. It pushes necessary strong references further down in the stream cleanup process to make their necessity clearer.
Attachment #625102 -
Flags: review?(benjamin)
Try server run: https://tbpl.mozilla.org/?tree=Try&rev=f4b4a651e203
Reporter | ||
Updated•12 years ago
|
Attachment #625102 -
Flags: review?(benjamin) → review+
pushed to mozilla-inbound http://hg.mozilla.org/integration/mozilla-inbound/rev/407014e60866
Comment 5•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/407014e60866
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla15
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•