Closed
Bug 49895
Opened 24 years ago
Closed 24 years ago
[MLK] Leaking a LeafNode (nsCString) in nsCategoryManager::AddCategoryEntry()
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
VERIFIED
FIXED
People
(Reporter: beard, Assigned: scc)
References
()
Details
(Keywords: memory-leak)
Attachments
(3 files)
145.67 KB,
text/html
|
Details | |
691 bytes,
patch
|
Details | Diff | Splinter Review | |
1.27 KB,
patch
|
Details | Diff | Splinter Review |
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. ***
Reporter | ||
Comment 2•24 years ago
|
||
Reporter | ||
Comment 3•24 years ago
|
||
This leak shows up when cookie is auto-registered.
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 4•24 years ago
|
||
Assignee | ||
Comment 5•24 years ago
|
||
Assignee | ||
Comment 6•24 years ago
|
||
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
Comment 7•24 years ago
|
||
please verify
Marking Verified. Please reopen if problem reoccurs.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•