Closed Bug 51595 Opened 24 years ago Closed 24 years ago

[MLK] Leaking nsBorderEdge objects

Categories

(Core :: Layout, defect, P2)

defect

Tracking

()

VERIFIED DUPLICATE of bug 33175

People

(Reporter: beard, Assigned: karnaze)

References

()

Details

(Keywords: memory-leak)

At the URL above, nsBorderEdge objects are being stored in an nsBorderEdges object, which contains an array of nsVoidArrays. Every one of these is leaking because in nsTableCellFrame::~nsTableCellFrame(), a simple delete of mBorderEdges is deleting the nsBorderEdges object, and the contained nsVoidArrays, but nothing is being done to delete the nsBorderEdge objects contained by the nsVoidArrays. There either needs to be explicit cleanup in nsTableCellFrame::~nsTableCellFrame(), or nsBorderEdges needs its own destructor to do the cleanup.
Keywords: mlk
karnaze has been looking into improving the collapsing border code. chris, we should either land your improvements (keeping in mind this bug to make sure it's not repeated in the new code), or put in the simple fix patrick suggests. one or the other should happen for beta3.
Assignee: buster → karnaze
Keywords: nsbeta3
Priority: P3 → P2
This is a dup of bug #33175 ....
*** This bug has been marked as a duplicate of 33175 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified dupe of bug 33175: "MLK: nsBorderEdge out of nsBorderEdges out of nsTableCellFrame::InitCellFrame()"
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.