Closed
Bug 192352
Opened 23 years ago
Closed 23 years ago
~ns{In,Out}putStreamReadyEvent should check nsIEventQueue::isQueueOnCurrentThread
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla1.4alpha
People
(Reporter: darin.moz, Assigned: darin.moz)
Details
(Keywords: memory-leak)
Attachments
(2 files)
|
4.08 KB,
patch
|
Details | Diff | Splinter Review | |
|
5.03 KB,
patch
|
dougt
:
review+
dougt
:
superreview+
|
Details | Diff | Splinter Review |
a better solution to bug 192196 would involve checking
nsIEventQueue::isQueueOnCurrentThread to see if it is actually ok to release
mNotify on the current thread, instead of leaking when PostEvent fails.
| Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.3beta
| Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla1.3beta → mozilla1.4alpha
| Assignee | ||
Comment 1•23 years ago
|
||
| Assignee | ||
Comment 2•23 years ago
|
||
| Assignee | ||
Updated•23 years ago
|
Attachment #117980 -
Flags: superreview?(dougt)
Attachment #117980 -
Flags: review?(dougt)
Comment 3•23 years ago
|
||
Comment on attachment 117980 [details] [diff] [review]
v1 patch (whitespace changes removed)
shouldn't this be debug only?
| Assignee | ||
Comment 4•23 years ago
|
||
no, i don't think so. the "let's just leak this shit" case should never be hit
in real code. but, otherwise it can definitely be the case that someone
constructs a {In,Out}putStreamEvent and never calls the On{In,Out}putStreamReady
method, which is what causes the event to be posted to the event queue. if that
method isn't called, then we need to have code to cleanup. this is that code :-)
Comment 5•23 years ago
|
||
Comment on attachment 117980 [details] [diff] [review]
v1 patch (whitespace changes removed)
okay.
Attachment #117980 -
Flags: superreview?(dougt)
Attachment #117980 -
Flags: superreview+
Attachment #117980 -
Flags: review?(dougt)
Attachment #117980 -
Flags: review+
| Assignee | ||
Comment 6•23 years ago
|
||
fixed-on-trunk
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•