OPEN SOURCE WEB BROWSER OUTFIT Mozilla has released yet another version of Firefox.
Firefox 3.6.6 is now available as a free download for Windows, Mac, and Linux here.
We are not quite sure why the outfit bothered. According to the bug list there was only one thing updated and that was a change to the crash protection feature introduced in Firefox 3.6.4. This increases the amount of time that Firefox will allow a plugin to remain frozen before killing it.
Earlier editions were less patient with errant apps and used to shut them down quickly. It hardly seems worthwhile as a release on its own. Someone must have got very cross with it.
A spokesman for Mozilla said, "Following the release of Firefox 3.6.4 we heard from some users, mainly those using older computers, that they sometimes expect longer periods of non-responsiveness from plugins, especially with games."
"For these users the default timeout of 10 seconds was too short. To address this, we increased the amount of time Firefox waits for a plugin to respond before terminating it from 10 to 45 seconds. This change has been made in Firefox 3.6.6, which was released today as an automatic update for all users," the spokesman said.
Still, we think it could have waited. µ
Why do they keep on working on this browser? OPERA is much better and has always been better and safer than FireFOX so what's the reason for FireFOX to exist?
I've known for a long time that 3.6.4 was the release with crash protection. Too long of a wait if you ask me. I'm glad it is finally here.
It's a small update taking no time at all to do, so why not do it?
@DeFex You can (and could) already change the value, it's available in the about:config settings under the name dom.ipc.plugins.timeoutSecs
And there was a discussion about the 45 secs too since that's so long that normal users will think the whole browser died and will kill it without waiting for it to revive itself by halting a buggy plugin, so you might want to lower the 45 value to something shorter, even the farmville players tested and found already that 30 secs was enough, but the guys at mozilla wanted to be sure and added another 15.
As for doing an update just for farmville, imagine how stupidly frustrating it is for someone to have the the browser kill a perfectly fine plugin? And I tried to play some HD youtube on somebody's slow computer (with onboard graphics) and flash crashed, but I think it was also just a timeout issue now caused by the system being overloaded and responding too slow.
Why not have a slider in the preferences so we non farmville players can adjust it?
quote from the bug discussion:
https://bugzilla.mozilla.org/show_bug.cgi?id=574905
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 out timeout to trigger and kill it.
[...snip...]
I can't believe Farmville is solely responsible for a Firefox update *facepalm*
/endquote
Still, we think it could have waited. µ
I think you'll find they waited 45 secs.