[ShadowAce]

[unspun]

thanks

[Straight Vermonter]

It's also worth noting that most of the attacks can be eliminated by blocking a site's ability to run Javascript. That means users of the NoScript add-on for Firefox will in many cases be protected against the attack. Then again, it's getting harder and harder to do anything online without Javascript.

I used to use noscript but I had to shut it for most sites just to view any content so what's the point?

[ken21]

firefox does not work on my 2 win 7 pcs.

it crashes often.

[TomGuy]

I’m less concerned about a history leak than the damn memory leak that has been persistent from version 0.7 to the current 3.5-3.6 versions.

I have tried a few of the memory clearing add-ons, but none of them actually work. The only method to clear the large wad of memory Firefox consumes and refuses to release is to shut Firefox down and restart it.

Some early versions of MS Word exhibited similar memory consumption, which it would not release until Word was closed. Microsoft eventually found a solution and plugged the leak. Too bad Firefox can’t seem to find a solution.

[GOPJ]

Thanks