Closed Bug 3146 Opened 26 years ago Closed 26 years ago

[CODE] Anonymous table frames cause leaking of content objects

Categories

(Core :: Layout: Tables, defect, P1)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: troy, Assigned: karnaze)

References

()

Details

(Whiteboard: 8/2: 5th request for reporter or assigned engineer to verify bug fixed)

This mush smaller snippet of HTML demonstrates the leaks: <UL style="display: table-row; background-color:orange;"> <LI style="display: table-cell; background-color:orange;">ONE</LI> </UL> Here's the Purify output. There's other stuff it mentions, but fixing the leaking of the content object should fix the other stuff as well: [W] MLK: Memory leak of 120 bytes from 2 blocks allocated in NS_NewTextNode(nsIContent * *) Distribution of leaked blocks Allocation location new(UINT) [new.cpp:23] NS_NewTextNode(nsIContent * *) [nsTextNode.cpp:89] SinkContext::FlushText(int *) [nsHTMLContentSink.cpp:1267] SinkContext::CloseContainer(nsIParserNode const&) [nsHTMLContentSink.cpp:995] HTMLContentSink::CloseContainer(nsIParserNode const&) [nsHTMLContentSink.cpp:1872] CNavDTD::CloseContainer(nsIParserNode const&,nsHTMLTag,int) [CNavDTD.cpp:2321] CNavDTD::CloseContainersTo(int,nsHTMLTag,int) [CNavDTD.cpp:2354] CNavDTD::CloseContainersTo(nsHTMLTag,int) [CNavDTD.cpp:2375] CNavDTD::HandleEndToken(CToken *) [CNavDTD.cpp:1165] NavDispatchTokenHandler(CToken *,nsIDTD *) [CNavDTD.cpp:252] [W] MLK: Memory leak of 64 bytes from 1 block allocated in NS_NewHTMLUListElement(nsIHTMLContent * *,nsIAtom *) Distribution of leaked blocks Allocation location new(UINT) [new.cpp:23] NS_NewHTMLUListElement(nsIHTMLContent * *,nsIAtom *) [nsHTMLUListElement.cpp:86] MakeContentObject [nsHTMLContentSink.cpp:700] CreateContentObject [nsHTMLContentSink.cpp:833] SinkContext::OpenContainer(nsIParserNode const&) [nsHTMLContentSink.cpp:953] HTMLContentSink::OpenContainer(nsIParserNode const&) [nsHTMLContentSink.cpp:1862] CNavDTD::OpenContainer(nsIParserNode const&,int) [CNavDTD.cpp:2264] CNavDTD::HandleDefaultStartToken(CToken *,nsHTMLTag,nsIParserNode&) [CNavDTD.cpp:887] CNavDTD::HandleStartToken(CToken *) [CNavDTD.cpp:995] NavDispatchTokenHandler(CToken *,nsIDTD *) [CNavDTD.cpp:250] [W] MLK: Memory leak of 64 bytes from 1 block allocated in NS_NewHTMLLIElement(nsIHTMLContent * *,nsIAtom *) Distribution of leaked blocks Allocation location new(UINT) [new.cpp:23] NS_NewHTMLLIElement(nsIHTMLContent * *,nsIAtom *) [nsHTMLLIElement.cpp:83] MakeContentObject [nsHTMLContentSink.cpp:616] CreateContentObject [nsHTMLContentSink.cpp:833] SinkContext::OpenContainer(nsIParserNode const&) [nsHTMLContentSink.cpp:953] HTMLContentSink::OpenContainer(nsIParserNode const&) [nsHTMLContentSink.cpp:1862] CNavDTD::OpenContainer(nsIParserNode const&,int) [CNavDTD.cpp:2264] CNavDTD::HandleDefaultStartToken(CToken *,nsHTMLTag,nsIParserNode&) [CNavDTD.cpp:887] CNavDTD::HandleStartToken(CToken *) [CNavDTD.cpp:995] NavDispatchTokenHandler(CToken *,nsIDTD *) [CNavDTD.cpp:250]
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Recent changes to frame construction may have fixed this. Purify does not indicate any table related memory leaks on the small test case.
Whiteboard: Requesting help with verification from engineer - unable to determine leaks
Chris - how can I verify this bug. I do not have access to Purify.
Chris K - please verify this bug fixed. I am unable to track leaks
Chris K - please verify this bug - I am unable to track leaks. Thanks
Target Milestone: M7
Whiteboard: Requesting help with verification from engineer - unable to determine leaks → 7/14: Followup request for reporter or assigned to engineer to verify bug
Troy or Chris K: Please verify bug as fixed - I am unable to track leaks.
Whiteboard: 7/14: Followup request for reporter or assigned to engineer to verify bug → 8/2: 5th request for reporter or assigned engineer to verify bug fixed
5th request for reporter or assigned engineer to verify bug fixed - I am unable to track leaks.
Status: RESOLVED → VERIFIED
Summary: Anonymous table frames cause leaking of content objects → [CODE] Anonymous table frames cause leaking of content objects
You need to log in before you can comment on or make changes to this bug.