Closed Bug 17394 Opened 27 years ago Closed 26 years ago

MLK: leaking nsDOMEvents while running editor

Categories

(Core :: DOM: Core & HTML, defect, P3)

All
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: warrensomebody, Assigned: joki)

Details

(Keywords: memory-leak)

Akkana Peck did this: setenv XPCOM_MEM_BLOAT_LOG 1 script apprunner -edit (typed a few characters, did Debug->Output HTML, then quit) ^D (to end the script) and said: We leak 9 nsDOMEvents, and 5 nsDocuments (plus 5 each of lots of html elements that are obviously coming from those leaked documents). Not sure where those are coming from (could be the editor, could be XUL). Vidur, can you investigate? [PTD team: we don't know the extent of the memory bloat due to this yet. We just know it's unnecessary.]
Assignee: vidur → joki
Handing over to Joki, since events are his domain.
Keywords: mlk
Using 3/1/2000 build on WINNT with bloaty enabled, I don't see any leakage of nsDOMEvents or nsDocuments. I loaded composer and typed several paragraphs. Marking fixed.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
warren Could you verify this one ?
You can verify by looking at the tinderbox bloat logs.
Marking verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.