Closed Bug 36957 Opened 25 years ago Closed 25 years ago

AtomImpl and nsStr leak introduced

Categories

(Core :: Internationalization, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dbaron, Assigned: cata)

References

Details

(Keywords: memory-leak, regression)

Yesterday evening (2000-04-23) between 19:00 and 20:30 (blame shows only cata%netscape.com , plus fixes for build bustage ) the tinderbox leak stats went up 2K: * AtomImpl leaks rose from 7 to 52 objects (difference of 45 objects) * nsStr leaks rose from 93 to 138 objects (difference of 45 objects) This looks like 45 nsMenuItem2 (which are not accounted for in the leak stats) might be leaking, since that class was introduced.
*** Bug 36943 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Target Milestone: --- → M16
I have a fix. I'll check in as soon as tree opens.
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Verified, based on tinderbox leak charts. But, should nsMenuItem2 have MOZ_COUNT_CTOR and MOZ_COUNT_DTOR macros so that it shows up in these stats?
QA Contact: teruko → cata
Cata, please read dbaron@fas.harvard.edu 's last comment. I changed QA contact to you.
Macros added. Thanks for the tip! Marking bug verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.