404 Tech Support

On Crash Protection and Farmville the Reason Behind Firefox 3.6.6

Mozilla Firefox 3.6.4 shipped June 22nd with a feature dubbed Crash Protection as well as a number of security and stability issues. From the Firefox 3.6.4 Release Notes:

Firefox 3.6.4 provides uninterrupted browsing for Windows and Linux users when there is a crash in the Adobe Flash, Apple Quicktime or Microsoft Silverlight plugins.

If a plugin crashes or freezes, it will not affect the rest of Firefox. You will be able to reload the page to restart the plugin and try again.

Unfortunately, crash protection caused a few web applications to time out before they would finish loading. Most notably of these web apps was Farmville, a “game” available a a Facebook application, and Hulu, a popular site for streaming video. From Bugzilla, the only thing addressed in the bug-fix release of Firefox 3.6.6:

However, now that 3.6.4 has shipped, we are seeing an increasing number of
reports that some users are unable to play Farmville, because Farmville hangs
the browser long enough for [our] timeout to trigger and kill it.

Originally, the Firefox plugin crash protection was set at 10 seconds. After a plugin has not responded for 10 seconds, the browser would kill the plugin and allow you to reload the page or restart the plugin. Unfortunately, these problematic web apps are taking longer than 10 seconds to load and the crash protection was kicking in before the plugin would respond. Firefox 3.6.6 has bumped the crash protection setting up to a 45 second time out and it has reportedly resolved the issues with Hulu and Farmville. Other apps may still be seeing issues if they take longer than 45 seconds to load at some points.

You can control the crash protection time out of your locally installed Firefox through the About:config.

Open a new tab and type about:config in the address bar and hit enter.

In the filter box, type dom.ipc.plugins.timeoutSecs.

When the Preference is found, you can double-click on it to adjust how many seconds the crash protection waits before kicking in. You can also set it to -1 in order to disable the new plugin crash protection.

This also introduces a new process that runs alongside Firefox now, whether you have Crash Protection disabled or not, called plugin-container.exe that takes up about 30 MB of memory from what I’m seeing.

In other news: Productivity around the world sky-rocketed for 4 days and then plummeted again to standard sub-par levels.