Could be the bad disk, bad profile, bad extension, anything really.. not enough info.
Since giving up on FF, I compile unofficial version of palemoon, it loads everything from tmpfs, works great for me at the moment.

Have you tried any other browsers to see if they also freeze?

running firefox with strace, combined with tcpdump sniffing packets on the interface, could render some clues...

I habitually run in excess of 50 tabs in a number of windows on whatever version -current has to offer. Previously tabs started to fail and eventually everything would terminate when total memory consumption exceeded 4 GB. This has recently changed and stability has increased greatly for me.

I have had no problems since i made that comment and closed all tabs so i guess it was one page that i had open in a tab that caused it.

1 members found this post helpful.

No issues here, Firefox runs with lots of open tabs for days until I reboot.
(running -current + xfce and the stock kernel, so I update regularly).

I believe the intent was to say one "specific tab" out of those that were open likely was to blame.

Not having "many open tabs" in general

I have long since discovered that the vast majority of web sites are malformed. Sometimes that just makes them ugly at the source level, but more often it makes them inefficient and slower to load. On Facebook in particular there are specific conditions when the page source becomes totally ridiculous. I discovered that I was able to totally lock up the page by replicating certain normal actions in the same order. Migrating to FireFox (mozilla) based browsers reduced the problem (the source was just as ugly, but it took more to lock it up) but the problem remained. I found three solutions that worked:
1. move to an alternate browser like Dillo, that simply do not support the most ugly of the page codes: this caused complaints from Facebook, but avoided lockup.
2. move to the mobile pages (m.facebook.com) which are fare more simple. This does not support all of the features, but avoids much of the ugly code.
3. Move to a different social media site. Few of them send code NEARLY as ugly as Facebook.

I had a fourth option, run Facebook using the traditional desktop. It was, on occasion, rather bad, but not NEARLY so bad as the new interface. Alas, Facebook has disabled the traditional interface and going back is no longer offered as an option.

In relation to THIS thread, my conclusion is that the problem may not be with the browser or rendering, but it may be with a badly malformed PAGE on the SITE! I have run into these so often that I have taken to calling it the HTML BOMB. I am not sure it is DESIGNED to blow up browsers, but it might as well be. Could it be that you have found such a page?

1 members found this post helpful.

LOL....

I couldn't agree more