Closed
Bug 3732
Opened 26 years ago
Closed 25 years ago
MLK:160 bytes leaked - Leaking form elements array
Categories
(Core :: Layout, defect, P3)
Core
Layout
Tracking
()
VERIFIED
FIXED
M17
People
(Reporter: bruce, Assigned: pollmann)
References
Details
(Keywords: memory-leak)
Build, pull from March 14, 1999.
MLK: 160 bytes leaked in 3 blocks
* This memory was allocated from:
malloc [rtlib.o]
__bUiLtIn_nEw [libgcc.a]
__builtin_new [rtlib.o]
__bUiLtIn_vEc_nEw [libgcc.a]
__builtin_vec_new [rtlib.o]
nsVoidArray::InsertElementAt(void*,int) [nsVoidArray.cpp:102]
nsVoidArray::AppendElement(void*) [nsVoidArray.h:52]
nsHTMLFormElement::AddElement(nsIFormControl*)
[nsHTMLFormElement.cpp:424]
nsHTMLInputElement::SetForm(nsIDOMHTMLFormElement*)
[nsHTMLInputElement.cpp:683]
SetForm(nsIHTMLContent*,nsIDOMHTMLFormElement*)
[nsHTMLContentSink.cpp:486]
MakeContentObject(nsHTMLTag,nsIAtom*,nsIDOMHTMLFormElement*,nsIWebShell*,nsIHTML
Content**,const nsString*) [nsHTMLContentSink.cpp:601]
CreateContentObject(const
nsIParserNode&,nsHTMLTag,nsIDOMHTMLFormElement*,nsIWebShell*,nsIHTMLContent**)
[nsHTMLContentSink.cpp:834]
SinkContext::AddLeaf(const nsIParserNode&) [nsHTMLContentSink.cpp:1050]
HTMLContentSink::AddLeaf(const nsIParserNode&)
[nsHTMLContentSink.cpp:1884]
CNavDTD::AddLeaf(const nsIParserNode&) [CNavDTD.cpp:2498]
CNavDTD::HandleDefaultStartToken(CToken*,nsHTMLTag,nsIParserNode&)
[CNavDTD.cpp:910]
CNavDTD::HandleStartToken(CToken*) [CNavDTD.cpp:1064]
NavDispatchTokenHandler(CToken*,nsIDTD*) [CNavDTD.cpp:247]
CTokenHandler::operator ()(CToken*,nsIDTD*) [nsTokenHandler.cpp:80]
CNavDTD::HandleToken(CToken*,nsIParser*) [CNavDTD.cpp:594]
CNavDTD::BuildModel(nsIParser*,nsITokenizer*,nsITokenObserver*,nsIContentSink*)
[CNavDTD.cpp:501]
nsParser::BuildModel() [nsParser.cpp:799]
nsParser::ResumeParse(nsIDTD*) [nsParser.cpp:751]
nsParser::OnDataAvailable(nsIURL*,nsIInputStream*,unsigned int)
[nsParser.cpp:963]
nsDocumentBindInfo::OnDataAvailable(nsIURL*,nsIInputStream*,unsigned
int) [nsDocLoader.cpp:1783]
stub_put_block(_NET_StreamClass*,const char*,int)
[nsStubContext.cpp:647]
net_read_file_chunk [mkfile.c:956]
net_ProcessFile [mkfile.c:1327]
NET_ProcessNet [mkgeturl.c:3371]
NET_PollSockets [mkselect.c:298]
* Block of 96 bytes at 0x6ca7e8
* Block of 32 bytes (2 times); last block at 0x6f9918
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M4
Updated•26 years ago
|
Target Milestone: M4 → M5
Comment 1•26 years ago
|
||
Moving to M5
Updated•26 years ago
|
Target Milestone: M5 → M6
Comment 2•26 years ago
|
||
Reassigning to Eric, moving to M6.
Comment 3•26 years ago
|
||
Moving to M8.
Updated•26 years ago
|
Assignee: karnaze → pollmann
Status: ASSIGNED → NEW
Comment 4•26 years ago
|
||
Reassigning to Eric.
Assignee | ||
Comment 5•26 years ago
|
||
I'm arbitrarily declaring M8 my UMR/MLK milestone. :)
Assignee | ||
Comment 6•26 years ago
|
||
I still haven't got Purify working on Solaris, and won't receive Purify for NT
for a few weeks. Marking these M10
Updated•25 years ago
|
Summary: MLK: Leaking form elements array → MLK:160 bytes leaked - Leaking form elements array
Assignee | ||
Comment 7•25 years ago
|
||
After careful consideration, I've decided that I probably won't get this bug in
for M12. Currently I have nearly 50 bugs scheduled for M13, so there is a
possibility that this bug may need to be moved out farther still.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M13 → M14
Assignee | ||
Comment 8•25 years ago
|
||
Triaged to M14
Assignee | ||
Comment 9•25 years ago
|
||
Moving off to M16 - please speak up of you need this for M14, thanks!
Assignee | ||
Updated•25 years ago
|
Target Milestone: M14 → M16
Assignee | ||
Comment 10•25 years ago
|
||
Rescheduling (*sigh*) Some of these are from M4. I wonder if they are all
still valid?
Target Milestone: M16 → M17
Assignee | ||
Comment 11•25 years ago
|
||
This has been fixed. See bug 36639. The form element and it's control list are
no longer leaked, unless you type in the URL bar. The URL bar leak is already
reported as a follow on to bug 24645.
Closing this one out as it has been taken care of!
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•