Closed Bug 192352 Opened 23 years ago Closed 23 years ago

~ns{In,Out}putStreamReadyEvent should check nsIEventQueue::isQueueOnCurrentThread

Categories

(Core :: XPCOM, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla1.4alpha

People

(Reporter: darin.moz, Assigned: darin.moz)

Details

(Keywords: memory-leak)

Attachments

(2 files)

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.
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.3beta
Target Milestone: mozilla1.3beta → mozilla1.4alpha
Attached patch v1 patchSplinter Review
Attachment #117980 - Flags: superreview?(dougt)
Attachment #117980 - Flags: review?(dougt)
Comment on attachment 117980 [details] [diff] [review] v1 patch (whitespace changes removed) shouldn't this be debug only?
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 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+
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.

Attachment

General

Creator:
Created:
Updated:
Size: