Re:Firefox 27 Released
by ndesaulniers on Tuesday February 04, 2014 @09:27PM
(#7181544)
> tab leaks it can freeze the whole browser
Process per tab is _almost_ ready: http://billmccloskey.wordpress.com/2013/12/05/multiprocess-f...
You can play with it by setting `browser.tabs.remote` to true in about:config.
I don't even want process per tab, I'd be happy with something much simpler: Tell me which tab is causing Firefox to use 100% CPU! This happens fairly frequently with lots of tabs open (I guess I use a lot of websites with really bad javascript) and the only recourse is to either quit Firefox entirely and re-open it, or play a guessing game.
Re:Firefox 27 Released
by ndesaulniers on Wednesday February 05, 2014 @05:46PM
(#7187416)
Firefox will stop any client side JavaScript after 5-6s and ask whether you want to keep running the slow running script or not. If will even change to that tab before prompting you. Isn't that what you just described?
I feel like Chrome is better when rendering stuff - like we've got this plotted graph in our app's admin, rendered with Javascript and I believe HTML5 Canvas or something, with too many points on it and Firefox can't handle the rendering, it chokes, whereas Chrome can do it. On the other hand, I feel like Firefox is snappier in general.