🚀 go-pugleaf

On Sun, 27 Nov 2011 11:36:18 +0000 (UTC), Bruce Esquibel <bje@ripco.com>
wrote:

>core <core-usenet@spamless.spook.homeip.net> wrote:
>
>> I tried Chrome for a couple of weeks, wasn't impressed. Went back to Firefox.
>> Never had it crash for me on any of the 5 or 6 boxes I run it on.
>
>
>I dunno about crashing but it (Firefox) does seem to have a memory problem.

I don't think it's FF itself. I think it's addons. The copy that's been up for
over 2 weeks has been memory stable. The copy on this machine does eat memory.
I restart it every few days.

>
>Since we don't run windows around here, the machines are rarely rebooted or
>shut down. Leaving FF running, even in the background doing nothing, one
>page open, it seems like after 3 or 4 days, it paralyzes the machine. Just
>getting it to quit takes a while.

I have 4 tabs up on the stable box. 2 running weather radar shots that update
constatly and the other two watching radio propagation maps that also auto
update regularly.

>
>This seems to be from last summer (2010), previous versions were fine but I
>guess when they started the ramp up to do "the release of the month",
>something was over looked.
>
>I mean I suppose if you are on a laptop or a desktop that is shut down
>periodically or normally quit the browser when done, it probably doesn't
>make any difference.
>
>But there is something wrong with it, I'm not the only one to make that
>observation.

Agreed.

/core