This leak happens when rendering a select menu for a form. Build from March 27, 1999. MLK: 1100 bytes leaked in 11 blocks * This memory was allocated from: malloc [rtlib.o] __bUiLtIn_nEw [libgcc.a] __builtin_new [rtlib.o] nsFrame::operator new(unsigned int) [nsFrame.cpp:163] NS_NewBlockFrame(nsIFrame*&,unsigned int) [nsBlockFrame.cpp:459] nsCSSFrameConstructor::ConstructFrameByDisplayType(nsIPresContext*,const nsStyleDisplay*,nsIContent*,nsIFrame*,nsIStyleContext*,nsAbsoluteItems&,nsFrameI tems&,nsAbsoluteItems&,nsAbsoluteItems&) [nsCSSFrameConstructor.cpp:2587] nsCSSFrameConstructor::ConstructFrame(nsIPresContext*,nsIContent*,nsIFrame*,nsAb soluteItems&,nsFrameItems&,nsAbsoluteItems&,nsAbsoluteItems&) [nsCSSFrameConstructor.cpp:2937] nsCSSFrameConstructor::ContentInserted(nsIPresContext*,nsIContent*,nsIContent*,i nt) [nsCSSFrameConstructor.cpp:3418] nsCSSFrameConstructor::RecreateFramesForContent(nsIPresContext*,nsIContent*) [nsCSSFrameConstructor.cpp:4571] nsCSSFrameConstructor::AttributeChanged(nsIPresContext*,nsIContent*,nsIAtom*,int ) [nsCSSFrameConstructor.cpp:3953] StyleSetImpl::AttributeChanged(nsIPresContext*,nsIContent*,nsIAtom*,int) [nsStyleSet.cpp:793] PresShell::AttributeChanged(nsIDocument*,nsIContent*,nsIAtom*,int) [nsPresShell.cpp:1626] nsDocument::AttributeChanged(nsIContent*,nsIAtom*,int) [nsDocument.cpp:1356] nsGenericHTMLElement::SetHTMLAttribute(nsIAtom*,const nsHTMLValue&,int) [nsGenericHTMLElement.cpp:665] nsHTMLOptionElement::SetIndex(int) [nsHTMLOptionElement.cpp:219] nsSelectControlFrame::Reset() [nsSelectControlFrame.cpp:709] nsSelectControlFrame::PostCreateWidget(nsIPresContext*,int&,int&) [nsSelectControlFrame.cpp:594] nsFormControlFrame::Reflow(nsIPresContext&,nsHTMLReflowMetrics&,const nsHTMLReflowState&,unsigned int&) [nsFormControlFrame.cpp:311] nsLineLayout::ReflowFrame(nsIFrame*,nsIFrame**,unsigned int&) [nsLineLayout.cpp:841] nsBlockFrame::ReflowInlineFrame(nsBlockReflowState&,nsLineBox*,nsIFrame*,unsigne d char*) [nsBlockFrame.cpp:2728] nsBlockFrame::ReflowInlineFrames(nsBlockReflowState&,nsLineBox*,int*) [nsBlockFrame.cpp:2610] nsBlockFrame::ReflowLine(nsBlockReflowState&,nsLineBox*,int*) [nsBlockFrame.cpp:1717] nsBlockFrame::ReflowDirtyLines(nsBlockReflowState&) [nsBlockFrame.cpp:1522] nsBlockFrame::Reflow(nsIPresContext&,nsHTMLReflowMetrics&,const nsHTMLReflowState&,unsigned int&) [nsBlockFrame.cpp:892] nsAreaFrame::Reflow(nsIPresContext&,nsHTMLReflowMetrics&,const nsHTMLReflowState&,unsigned int&) [nsAreaFrame.cpp:509] nsContainerFrame::ReflowChild(nsIFrame*,nsIPresContext&,nsHTMLReflowMetrics&,con st nsHTMLReflowState&,unsigned int&) [nsContainerFrame.cpp:388] nsTableCellFrame::Reflow(nsIPresContext&,nsHTMLReflowMetrics&,const nsHTMLReflowState&,unsigned int&) [nsTableCellFrame.cpp:501] nsContainerFrame::ReflowChild(nsIFrame*,nsIPresContext&,nsHTMLReflowMetrics&,con st nsHTMLReflowState&,unsigned int&) [nsContainerFrame.cpp:388] nsTableRowFrame::InitialReflow(nsIPresContext&,nsHTMLReflowMetrics&,RowReflowSta te&,unsigned int&,nsTableCellFrame*,int) [nsTableRowFrame.cpp:808] nsTableRowFrame::Reflow(nsIPresContext&,nsHTMLReflowMetrics&,const nsHTMLReflowState&,unsigned int&) [nsTableRowFrame.cpp:1418] * Block of 100 bytes (11 times); last block at 0x817528

I'm arbitrarily declaring M8 my UMR/MLK milestone. :)

I still haven't got Purify working on Solaris, and won't receive Purify for NT for a few weeks. Marking these M10

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.

QA Contact update.

Triaged to M14

Moving off to M16 - please speak up of you need this for M14, thanks!

Rescheduling (*sigh*) Some of these are from M4. I wonder if they are all still valid?

The original testcase provided is now not available. Since the description is "rendering a select menu for a form", I'm marking this WORKSFORME since we don't leak any nsFrame objects loading the bugzilla query page, and that's got all types of selects on it. This bug is very old, and I think it's probably more productive to just find leaks than to try and figure out what this was (since it's almost definitely fixed now).

Updating QA contact.

Verifying as for developer's coments