[nnethercote]

Resetting might help: https://support.mozilla.org/en-US/kb/reset-firefox-easily-fi...

It resets your profile while preserving history, cookies, bookmarks, etc.

> I'm really looking forward to the new threading model coming up. I have a feeling that once each tab has a thread, things like this will be much more self-repairing. It's not always easy to kill a rogue execution path in an event loop, but killing a thread is pretty straightforward =].

First, it's "process", not "thread" :)

The plan is to start with just two main processes -- one for chrome (browser UI, mostly) and one for web content. So no processes will be killed in normal operation. This is because additional processes incur certain extra costs, particularly when it comes to memory consumption.

Still, it might help with your problem; it's hard to say for sure.