Builds from March 8 - March 11, 1999 at the least produce this. MLK: 4032 bytes leaked in 126 blocks * This memory was allocated from: malloc [rtlib.o] __bUiLtIn_nEw [libgcc.a] __builtin_new [rtlib.o] NS_NewTimer(nsITimer**) [nsTimer.cpp:176] nsCaret::PrimeTimer() [nsCaret.cpp:211] nsCaret::CaretBlinkCallback(nsITimer*,void*) [nsCaret.cpp:373] TimerImpl::FireTimeout() [nsTimer.cpp:73] nsTimerExpired [nsTimer.cpp:188] g_timeout_dispatch [gmain.c:1147] g_main_dispatch [gmain.c:647] g_main_iterate [gmain.c:854] g_main_run [gmain.c:912] gtk_main [gtkmain.c:475] nsAppShell::Run() [nsAppShell.cpp:152] nsAppShellService::Run() [nsAppShellService.cpp:154] main [nsAppRunner.cpp:286] _start [crt1.o] * Block of 32 bytes (126 times); last block at 0x707f50

This may be a bug in the GTK timer implementation.

This is a GTK leak. Reassigning for closure.

fix checked in.

marking fixed.

Changing a few bugs at once...This is a bug that I have determined I am unable to properly verify. More than likely this would be because it is outside my expertise or experience, or i don't have the necessary tools. I am now ASKING PLEASE, please could the bug owner or reporter take it upon themselves to verify the fix for this bug and mark it VERIFIED? Don't be shy, step right up. Thank you.

Per a request from Selection and Search component eng (mjudge) and qa (elig), moving all "Selection and Search" bugs to new "Selection" component. Original "Selection and Search" component will be retired.