🚀 go-pugleaf

Adam H. Kerman <ahk@chinet.com> wrote:
>Kristian M Zoerhoff <kristian.zoerhoff@gmail.com> wrote:
>>On 2011-11-28, Adam H. Kerman <ahk@chinet.com> wrote:
>>>core <core-usenet@spamless.spook.homeip.net> wrote:
>>>>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.

>>>I thought it was goddam instances of Flash that never end; stupid plugin
>>>design. They run outside the browser process.

>>*cough* FlashBlock *cough*

>One of my most useful add ons, together with Noscript and Redirect
>Remover. Also, I don't open pdfs in the browser, ever; those get saved to
>a file. But, yes, when I have allowed Flash to run, the instances don't
>necessarily end when I leave the Web page or even when I close the browser
>application. Flash sucks.

Just noticed the problem yesterday. I've got the latest firefox, 8.0
under the new version inflation regime; I was just runing 3.6 in the spring.
I'd shut down firefox. A few hours later, I opened what I expected would
be a new instance of firefox, but it was behaving like an additional window
with an old instance of firefox. I can tell because I had allowed temporary
permission to run javascript under NoScript at a specific Web site and
I didn't have to grant temporary permission again when I next looked at
the same site.

I tried to end the application. In Task Manager process list, there were
two instances of plugin container and one instance of firefox. Even after
ending both plugin container instances, the other firefox process still
didn't terminate nicely, so I ended that as well.

So, no, it's still not fixed. Are these new firefox versions making anything
more than cosmetic changes? Is it all essentially 3.6 technically?