IIRC in 7 they messed up the Sync feature that allowed them to ask browsers to stop slamming their servers. So sync was messed up in 7, just not the way you might think. 6 just said "Oh, you don't want me to bother you? Okay.. ;("

If you get the freezing up issue this fixes it.

Need to do both of these.

Type about:config into your address bar, accept the warning, type in the Filter box network.http.max-connections


Then double click on the network.http.max-connections setting and
change the value to 32 (default was set to 256 from FF version 6.0
upwards).

follow the instructions here
http://blog.bonardo.net/2011/09/30/is-your-firefor-freezing-at- regular-intervals

 

-----signature-----

^

Depends on what is causing it. I was able to reproduce a bug to push the amount of memory Firefox uses to almost 2GB. I stopped at that point but doubtless could have gone further. Not sure if it was something wrong on Amazons end, or FF but its suspect

I had tried those, and it didn't work. My freezing wasn't at 'regular' intervals, though. There didn't seem to be a pattern to it. Moot point though, since there was a change in 8 which removes or alters the cause of the freezing entirely. Working fine so far.

 

-----signature-----

That feature was broken in 6 too. Which is why I was puzzled why Firefox 7 seemed to have freeze up issues and not Firefox 6. Even when I turned off Sync I still had Firefox 7 freezing up, which is probably why I never reinstalled it even after they fixed Sync.

Which is as it should be but rarely is. You shouldn't have to relearn a piece of software just because it has been updated.

 

-----signature-----

I think you are missing his point. If nothing has changed, does it really merit a major version change? Answer: only until its "higher" than chrome or ie!

What do you mean "nothing has changed". Did you not see Twitter in your search bar now?

Meaningless if you do not use Twitter.

 

-----signature-----

I think acao needed a /sarcasm tag