From: "Gary Britt" 

Your points are all valid behavior wise.  Its not a stub in memory, it
appears to be the entire firefox.exe program left in memory and performing
i/o reads and writes.  I don't have a firefox fast launch component that
I'm aware of anyway.  I don't seen it any of the normal places as far as I
know. On my computer firefox loads initially and loads pages faster than
IE.

I wonder if the problem is related to the faster fox extension I installed,
it tries to preload items from links on various pages and might be the
cause.  I'll have to check that out.

Gary

"Frank Haber"  wrote in message
news:44d7477e$1{at}w3.nls.net...
> 1. I could say, "Don't obsess," but you know how much good
that would do.
>
> 2. There have been memory leaks galore in FF.  You could let the sliver
> run and see whether its footprint grows.
>
> 3. It may just be a "fast launch" component.  Notice how FF
is MUCH slower
> to start the first time than IE?  That's because IE cheats, and loads
> stuff at boot.  After the first use, I think FF cheats, too.  You may want
> that little slice of EXE/DLL to stay there.
>
> 4. Don't close your browser so much. (I do that, too.  I still use Windows
> as a task switcher some of the time; 1-2G of RAM haven't stopped me.
> It'll take a bigger wooden mallet than that, I guess, to completely crush
> the habit.)

--- BBBS/NT v4.01 Flag-5