Closed Bug 49895 Opened 24 years ago Closed 24 years ago

[MLK] Leaking a LeafNode (nsCString) in nsCategoryManager::AddCategoryEntry()

Categories

(Core :: XPCOM, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: beard, Assigned: scc)

References

()

Details

(Keywords: memory-leak)

Attachments

(3 files)

See the blame URL above. If category->find_leaf(aEntryName) returns a non-NULL entry and aReplace is true, then the already existing entry will leak. I've seen this leak crop up occasionally, but it only happens during autoregistration, and I don't always detect it reliably.
*** Bug 49001 has been marked as a duplicate of this bug. ***
This leak shows up when cookie is auto-registered.
Keywords: mlk
Status: NEW → ASSIGNED
Attached patch leak fix patchSplinter Review
fix checked in with version 1.18 of the file ... though the patch contained tabs, I fixed that before checking in. Thanks, Patrick!
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
please verify
Marking Verified. Please reopen if problem reoccurs.
Status: RESOLVED → VERIFIED
Component: XPCOM Registry → XPCOM
QA Contact: leger → xpcom
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: