This happens once you get 2 options on a select element for a form. This does not happen with only one option in the select. Pull/build from March 27, 1999 (been happening a lot longer). MLK: 616 bytes leaked in 11 blocks * This memory was allocated from: malloc [rtlib.o] __bUiLtIn_nEw [libgcc.a] __builtin_new [rtlib.o] nsBlockFrame::AppendNewFrames(nsIPresContext&,nsIFrame*) [nsBlockFrame.cpp:3545] nsBlockFrame::SetInitialChildList(nsIPresContext&,nsIAtom*,nsIFrame*) [nsBlockFrame.cpp:4836] nsCSSFrameConstructor::ConstructFrameByDisplayType(nsIPresContext*,const nsStyleDisplay*,nsIContent*,nsIFrame*,nsIStyleContext*,nsAbsoluteItems&,nsFrameI tems&,nsAbsoluteItems&,nsAbsoluteItems&) [nsCSSFrameConstructor.cpp:2684] 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 56 bytes (11 times); last block at 0x817cb0

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 function AppendNewFrames doesn't exist anymore. It looks like it might have been replaced by AddFrames, which does not use operator new directly, anywhere. Is this bug worth keeping open?

Nope.

Based on above closing this one out!

Updating QA contact.

Verified as for developer's coments