Multiprocess is not enabled; Win6 FF 54.0 64 bit
I got Add-on compatibility viewer, it tells me one add-on is not compatible (Nuance PDF Create 2). I do not see an option to remove that add-on. I have disabled it and restarted, etc., and it still says that MP is not enabled and does list that one as incompatible.
MUST it be removed, or is disabling it enough? And if it must be removed, if it doesn't give a remove option from the add-on screen, how can I get rid of it? Note: I do NOT intend to get rid of the program, although I am willing to remove it from firefox.
Todas as respostas (9)
Extensions that do not have a "Remove" button are installed globally by other software and are not under control of the Firefox extension manager. Globally installed extensions are usually found via a registry scan or are installed in a location that Firefox scans for installed extensions.
- https://developer.mozilla.org/Installing_extensions
- https://developer.mozilla.org/Adding_Extensions_using_the_Windows_Registry
Extensions installed globally need to be removed via the settings (Options/Preferences) of the program that has added this extension or this program has to be uninstalled via "Control Panel -> Programs". In Firefox you can only disable such an extension.
Check its install location in the extensions.json file in the profile folder. You can open the extensions.json file in the Scratchpad and search for this extension. The descriptor field should list its install location.
You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.
- Help -> Troubleshooting Information -> Profile Directory:
Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder - http://kb.mozillazine.org/Profile_folder_-_Firefox
OK. FIRST I went to the program, and unchecked integrating with FF. That did not remove it.
Then I removed it from the registry and restarted FF. It is NOT listed anymore, and ALL of my extensions are compatible with multi-process.
YET, it still shows that MP is not enabled. Why not? (Note: I installed the same firefox on another computer and it IS enabled there. That one doesn't have Nuance so it was never included, although it does have some other extensions.)
What is the message you see in "Help -> Troubleshooting Information" (about:support)?
Is this still disabled by add-ons?
Note that there is a force setting (browser.tabs.remote.force-enable, New -> Boolean) on the about:config page, but this needs to be used only as a last resort as this can break things.
Not sure what you're looking for; there's a ton of stuff there.
I see a button to give firefox a tuneup -- the button says "refresh firefox", and pressing it says it removes add-ins and customizations, and restores everything to defaults.
Then there's "try safe mode", and the button says "restart with add-ons disabled".
I read about forcing it with:
Type and search for the preferences : browser.tabs.remote.autostart and set it's value to true browser.tabs.remote.autostart.2 and set it's value to true
For me, the first one is false. BUT I was hesitant to do it since I don't know why it is being disabled.
OH, maybe I found what you wanted:
Multiprocess Windows 0/1 (Disabled by accessibility tools)
Where do I have accessibility tools? OK, I also see:
accessibility.lastLoadDate 1497919221
accessibility.loadedInLastSession true
accessibility.typeaheadfind.flashBar 0
And something telling me to set that to FALSE, but I don't know what it means.
See this article for some information:
So I'm reading that they won't use multiprocess if a password manager is used, and/or if a screen scraper is used?
Guess I stop using FF again. I haven't used it in ages except as a test with some other browser isn't working. I read about this new release, and since my Chrome is eating CPU and RAM on a PC with plenty of both, I installed it and tried it. It actually failed badly both on the computer that had multiprocess and the one that didn't, but I at least wanted to leave it enabled. So now I guess I removed that PDF support for nothing if it won't work if you have either a password manager and a screen scraper (I use Snagit for the latter). I have used the password manager for FF; haven't used snagit in FF but I do use it elsewhere.
I can't understand why it won't do the MP if you use either, but I'd rather keep them and not use MP... and since the one place I really wanted FF to work is worse than Chrome, now there's no reason to try it with all my other sites.
Tnx, and maybe I'll try it again in another few years.
Hi BDSolomon !
Don't give up on Firefox just yet !
You could try and enable (not 'force-enable') Multi process (e1os) as follows :
Type in the address bar about:config (promise to be careful, if asked) Type and search for the preferences :
browser.tabs.remote.autostart and set it's value to true (You mentioned this one to be set to false)
browser.tabs.remote.autostart.2 and set it's value to true
Note: the exact name of the preference may vary, but it will start with browser.tabs.remote.autostart
Alterado por Happy112 em
I knew I could do that, but now that I worked out that the problem was the accessibility tools, which once identified as snagit and a key manager, I can confirm that I DO use, I was afraid that there was a good reason for that, so was concerned that I would break something if I did what you suggested (and I knew that I could do), and forced it to use MP with such tools.
I was also a little concerned that even if such tools didn't break it, it would keep setting that back to false as it rediscovered that I am using such tools.
Note that browser.tabs.remote.autostart is best to be left to false all the time. This is the main MP pref and will be set to true when this feature has been fully implemented. The other pref browser.tabs.remote.autostart.2 can be seen as an opt-in pref to allow using MP for now.
When external software needs to access content in a Firefox window then this is only possible when MP is disabled because all window content is in a sandbox container that doesn't allow access from the outside.