News for hackers. Stuff that matters.
Re:Firefox 31.0 by zimbatm on Tuesday July 22, 2014 @11:54AM (#8069620)
The only thing I want from Firefox is to stop freezing completely when a single tab goes crazy. It just makes the whole experience feel clunky compared to Chrome.

Usually it happens with Gmail so maybe there is a conspiracy there to drive adoption for Chrome :p

Re:Firefox 31.0 by potshot on Tuesday July 22, 2014 @12:50PM (#8069974)
Have you tried using multi-process tabs? http://www.ghacks.net/2014/02/13/firefoxs-multi-process-arch...

It looks like the prefs to enable it have been shipping beyond the nightly and are in the latest release.

Re:Firefox 31.0 by zimbatm on Tuesday July 22, 2014 @01:26PM (#8070273)
I didn't know about this. Hopefully it's stable.

EDIT: looks fairly stable. Back to Firefox.

Re:Firefox 31.0 by kipple on Tuesday July 22, 2014 @01:04PM (#8070086)
Oo neat I didn't know this was an option for FF
Re:Firefox 31.0 by cpeterso on Tuesday July 22, 2014 @04:20PM (#8071345)
Multi-process Firefox (aka Electrolysis or just e10s) is till under development. If you want to test it, I recommend using Firefox Nightly (34) because it has recent e10s bug fixes and its File menu has a "Open e10s Window". You can test e10s and non-e10s windows without flipping an about:config pref or restarting Firefox. You can flip the optional pref browser.tabs.remote.autostart to true to enable e10s by default, which also enables extra "shims" for add-on compatibility so more add-ons will work than with "New e10s Window".
Re:Firefox 31.0 by mistermann on Tuesday July 22, 2014 @02:28PM (#8070711)
Do you think this might solve some of the stability (memory) issues so many people have been seeing since the last release?
Re:Firefox 31.0 by mburns on Tuesday July 22, 2014 @01:06PM (#8070099)
Re:Firefox 31.0 by kipple on Tuesday July 22, 2014 @01:02PM (#8070076)
Chrome uses a separate render process for each tab[1], so when one crashes it doesn't KO the whole browser. However this also means Chrome has a larger memory footprint, since each tab is taking up the resources of a little browser. Firefox doesn't do this, and so it keeps a smaller memory footprint than Chrome (oh how times change) but the downside is--as you mentioned--the whole browser freezes if one tab fails.

[1] http://www.chromium.org/developers/design-documents/process-...

Re:Firefox 31.0 by cpeterso on Tuesday July 22, 2014 @09:11PM (#8072430)
The number of tabs per Firefox content process will, AIUI, be configurable via an about:config pref.
Re:Firefox 31.0 by Curmudgel on Tuesday July 22, 2014 @05:40PM (#8071724)
Try changing the values of dom.max_script_run_time and dom.max_chrome_script_run_time in about:config to lower values so that unresponsive scripts can be killed faster.
Re:Firefox 31.0 by zobzu on Tuesday July 22, 2014 @03:26PM (#8071081)
tbh this happens to me more often in chrome than firefox these days.. i do get slowdowns in firefox when some tabs are loading tho. but the complete freeze in chrome is when the ui or something goes wrong, its rarely a single tab (which doesnt really happen in firefox)