It's here already, in Nightly: https://nightly.mozilla.org/ (more info: https://wiki.mozilla.org/Electrolysis).
I haven't really had the problem you're talking about in Firefox as it is, but you can try it out and see if Nightly is any better. Keep in mind that Nightly is slower overall than Firefox, because it has a number of debugging flags enabled that impact performance.
Obligatory disclaimer: Nightly has lots of bugs and quirks compared to Firefox, so it should not be considered indicative of the normal Firefox experience[0]. Also, many extensions have not yet been ported (which is why it's available in Nightly for developers before hitting Firefox).
[0] That said, it's pretty damn stable. I'd be using it for my daily browsing except that I can't live without Vimperator, which hasn't yet been ported to e10s: https://github.com/vimperator/vimperator-labs/issues/211
That said, we should have a go/no-go on Monday for uplift with Firefox 40. We're getting Very Close Now. :)
FWIW in Servo when talking of multiprocess stuff we colloquially call it "Electrolysis". I think Patrick has some work in progress on this. It's not as much work as the Firefox e10s (we already use threads and channels for everything), but I think there is some (relatively) minor work to be done.
(ie that it wont be remoting everything and only protect the system from escaping a child - makes sense in firefox/chrome, less with rust being the compiler i guess)
I suspect that if servo doesnt try to be an OS like firefox/chrome do, a whole process sandbox may even be fine enough. But if it does.. :)
[1] - https://www.phoronix.com/scan.php?page=news_item&px=MTgzNDA