Pale Moon plugin-container.exe run when it should be disable

[ascii_elite]

Using Pale Moon 3.6.30, when browsing a page with Adobe Flash content (I have not tested for other plug-ins), plugin-container.exe runs when preference dom.ipc.plugins.enabled is set to false. The dom.ipc.plugins.enabled preference should control whether the plugin-container.exe can be used by Firefox (and it would seem that also should Pale Moon).

This seems to be a bug.

Please correct the problem or let me know how I could be of assistance so that the problem can be resolved.

EDIT: The problem maifested while running Windows XP Professional with Service Pack 2.

[satrow]

I really don't know much about this and I can't easily test on this machine right now.

Have you toggled dom.ipc.plugins.enabled.npswf32.dll ?

[ascii_elite]

I really don't know much about this and I can't easily test on this machine right now.

I note that Firefox/Pale Moon should not use plugin-container.exe process on Windows 2000, regardless of the value of dom.ipc.plugins.enabled.

Have you toggled dom.ipc.plugins.enabled.npswf32.dll ?

No. I have left all the preferences with names beginning "dom.ipc.plugins.enabled" at default values except sometimes dom.ipc.plugins.enabled (where default value may vary).

I set dom.ipc.plugins.enabled explicitly to false in "%ProgramFiles%\Pale Moon\defaults\profile\prefs.js" before user profile creation.

[satrow]

Then maybe you should try it?

I can't test it on W2K and me testing it on XP SP2 is out until maybe tomorrow or even later.

[ascii_elite]

Then maybe you should try it?

I had originally found the information on how to disable the Out of Process Plug-ins behavior sometime during year 2011 from the mozillaZine article http://kb.mozillazine.org/Plugin-contai ... ss_plugins .

EDIT: I also originally tested the plugin container behavoir on the 6 series of version of Firefox (which only includes a plugin container override variable for Java).

Perhaps the information at the time regarding the disabling of the plugin container was erroneous. The page seems to have been updated (going by the last modified date at its bottom).

There is still some erroneous information. For example, the article does not correctly represent behavior for Windows 2000 (for which case plug-in container would not be used (this may or may not be a bug)).

It seems that it is best to test the various behaviors for the Firefox 3.6 series (3.6.4 and above) and the Firefox 4+ series to determine Firefox/Pale Moon behavior.

[Moonchild]

The behavior is as-documented, ascii.

If you set dom.ipc.plugins.enabled to false, it means the default is to not use OOPP.
Specific dom.ipc.plugins.enabled.* parameters are there to override default behavior.

Windows 2000 does not have a special case scenario.

More information for 3.6.30: http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins#Firefox_3.6.x

[ascii_elite]

If you set dom.ipc.plugins.enabled to false, it means the default is to not use OOPP.
Specific dom.ipc.plugins.enabled.* parameters are there to override default behavior.

This is much more concise and to the point than the mozillaZine article.

After doing some testing on Windows XP Professional with Service Pack 2, I have verified this to be the case on the tested operating system.

Windows 2000 does not have a special case scenario.

This may mean that the out of process plug-in behavior is defective. On Windows 2000, I have never noticed the plugin container running (and I have often checked) for different versions of Firefox and Pale Moon (though I have not tried any version starting "8.").

More information for 3.6.30: http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins#Firefox_3.6.x[/quote]