Setting Dom.ipc.plugins.asyncinit in FF 40.0 causes Flash games (e.g. Farmville) to stop working properly
Since Firefox version 40.0 was released the Flash game Farmville no longer functions correctly. The game appears to load properly, but when you try to click on various items the expected action does not occur. All other browsers IE, Chrome, Waterfox etc. all work without this problem. (The failure is described in the Farmville forums as "the craft shops no longer open when you click on them".) It would appear to be the direct result of the changes made by Aaron Klotz to the way asynchronous plugins intialization works. When the flag Dom.ipc.plugins.asyncinit changed from it's previous default setting of False to True in version 40 is when the problems appeared. Reading Aaron's notes on his changes would suggest the fault may be the result of certain parts of the code being executed in the wrong order. By resetting this flag back to False all the problems go away. I can happily change the flag back, but most of the people who play Farmville do not have a detailed knowledge of computing and should not be expected to have to make such a change.
Modified by KatieLu
All Replies (7)
Supposedly this gets fixed by Hotfix 20150818.01 for bug 1196000, but it seems that if you have version 39 when you get the Hotfix, it will do nothing as the setting for Dom.ipc.plugins.asyncInit is already set to false. If you then update to FF 40.0.2, the new version of FF will reset that to True and you will again be stuck with a lot of Flash based stuff that doesn't work. It may also be the case if you have FF 40.0, the Hotfix will run and correct the value to false, but again, updating to version 40.0.2 will reset it to true.
I'm beginning to wish I never looked at this,
Katie that is true. I am running beta and the default was not what you first mentioned. It does change back. Post back if you have any other questions.
Please also update to version 40.0.2
Hi KatieLu, you said:
It may also be the case if you have FF 40.0, the Hotfix will run and correct the value to false, but again, updating to version 40.0.2 will reset it to true.
That shouldn't happen, because in Firefox 40, "false" would be a customized setting, and updates rarely change settings that have been customized from their default values. It may happen occasionally; I haven't tested this particular one myself.
jscher2000 said
Hi KatieLu, you said:It may also be the case if you have FF 40.0, the Hotfix will run and correct the value to false, but again, updating to version 40.0.2 will reset it to true.That shouldn't happen, because in Firefox 40, "false" would be a customized setting, and updates rarely change settings that have been customized from their default values. It may happen occasionally; I haven't tested this particular one myself.
It's a bit confusing as to what the Hotfix is actually doing. It appears to be a "run once" fix that gets applied to your current version of Firefox.....but after that if you subsequently update to either 40 or 40.0.2 you will be getting a version that reverses the value back to True, undoing the Hotfix. Quite a few people reverted back to FF 39.0.3 when they had problems with 40 & 40.0.2 and may be completely unaware of the actual details of the problem with the Dom.ipc.plugins.asyncInit setting. If they switch back on their automatic updates - which will they get first ? The hotfix or 40.0.2 ? I tried to simulate that situation, by reverting to 39 and re-updating and I ended up with the asyncInit flag showing as Default = True. For me it doesn't matter, I can reset that, but I'm wondering what about everyone else. Why hasn't the FF40.0.2 update/download file been fixed ? Or why isn't there a FF 40.0.3 with the fix ?
I don't know who can answer these questions. To my knowledge, it's only the second use of hotfix since the idea was developed.
jscher2000 said
I don't know who can answer these questions. To my knowledge, it's only the second use of hotfix since the idea was developed.
FF 40.0.3 has arrived with the Dom.ipc.plugins.asyncInit default set back to false, so I guess that sorts out all the possible problems that might have occurred if the Hotfix wasn't running at the right point.