Closed Bug 28979 Opened 26 years ago Closed 26 years ago

MLK: nsProfile::SetProfileDir() is leaky!

Categories

(Core Graveyard :: Profile: BackEnd, defect, P3)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bruce, Assigned: gayatrib)

Details

(Keywords: memory-leak)

nsProfile::SetProfileDir() allocates a ProfileStruct. It then fills it with some data (which it copies). It never deallocates any of that memory. Additionally, it passes that struct into nsProfileAccess::SetValue(). That goes and copies the data again. It is also leaky! It too creates objects when it doesn't get rid of in the error cases. This is adding noise to the leak reports and should be fairly simple to fix.
Not recommending for beta1.
Assignee: selmer → racham
not serious enough to mark beta1.
Target Milestone: M15
Status: NEW → ASSIGNED
Reassigning to gayatri.
Assignee: racham → gayatrib
Status: ASSIGNED → NEW
checked in fix.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
verified code fix
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.