Ever since around v. 2020.12, there's in an incompatibility with Classic's AccessibleHandler.dll on certain Windows patch levels. This causes the checkbox for Multiprocess mode to be greyed out. Force-enabling this via boolean will result in an immediate appcrash at startup.
The solution, as pointed out by others on Github is to replace AccessibleHandler.dll in the application directory with the dll from an older version. For convenience, I've attached the affected dll from 2020.09.
After replacing it, the option to toggle multiprocess mode may still be greyed out. If so, create the following boolean in about:config
browser.tabs.remote.force-enable
and set it to true
It should now be enabled after restarting the browser. Simply uncheck Recommended Performance Settings and choose the number of content processes to your liking
Remember to disable automatic updates!
I advise creating a scratch profile to test this on first, to avoid potential data loss in case of complications. It shouldn't be an issue, but just in case.....
(tested with Wf Classic 2021.03 on 7 x64)
Solution for Wf Classic Multiprocess Crash / Greyed Out
Solution for Wf Classic Multiprocess Crash / Greyed Out
- Attachments
-
- fix waterfox classic e10s multiprocess.zip
- (70.01 KiB) Downloaded 202 times
Precision 5810 - Xeon E5-1650 v3 | 16 GB | EVGA 970 | 840 Pro | 2 TB HGST | | 4 TB X300 | Vista-tweaked W7
Latitude e7250 - i7 5600U | HD 5500 | 16 GB | 250 GB mSATA | 1 TB My Passport | Vista-tweaked W7
Latitude e7250 - i7 5600U | HD 5500 | 16 GB | 250 GB mSATA | 1 TB My Passport | Vista-tweaked W7
- K4sum1
- Lazy Owner
- Posts: 992
- Joined: 11 Jan 2021, 07:40
- Location: ur dads house
- OS: Windows 8.1 x64
- Has thanked: 657 times
- Been thanked: 289 times
- Contact:
Solution for Wf Classic Multiprocess Crash / Greyed Out
I'm curious to see if accessibility.force_disabled is a potential fix.
I don't know what I'm doing hit album by Brad Sucks
Who is online
Users browsing this forum: No registered users and 1 guest