Izimpendulo zakamuva ze-All webpages show up as garbage texthttps://support.mozilla.org/zu/questions/12895892020-06-09T11:44:59-07:00tried browser.tabs.remote.autostart=false or true, this made no difference
MOZ_FORCE_DISABLE_E10S is2020-06-09T11:44:59-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1322286<p>tried browser.tabs.remote.autostart=false or true, this made no difference
</p><p>MOZ_FORCE_DISABLE_E10S is not on my system
</p><p>This bug was fixed for ver 78 Windows 10, I'm still using Windows 7.
</p><p>Will go back to stable ver 76 for my system. This has consumed a great amount of my time. Will wait to a later upgrade maybe it will work correctly then.
</p><p>cor-el --Thanks for all your help
</p>Could be this bug, affects ver 77 but not ver 76
https://bugzilla.mozilla.org/show_bug.cgi?id=1638652020-06-09T11:14:15-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1322275<p>Could be this bug, affects ver 77 but not ver 76
</p><p><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1638652" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1638652</a>
</p>ok checked accessibility
Activated = false
Prevent accessibility = 0
accessibility handler used = tr2020-06-09T11:06:01-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1322274<p>ok checked accessibility
</p><p>Activated = false
</p><p>Prevent accessibility = 0
</p><p>accessibility handler used = true
</p><p>accessibility Instantiator = blank
</p><p>Multiprocess Windows = 0/1 Disable forcibly
</p>Note that it isn't recommended to downgrade a profile as it isn't guaranteed that the profile is sti2020-06-08T15:33:14-07:00cor-elhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1321856<p>Note that it isn't recommended to downgrade a profile as it isn't guaranteed that the profile is still fully compatible.
</p>ok finally got it to work. Hope this helps someone else. After doing lots of digging.
"You'll have t2020-06-08T14:00:25-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1321845<p>ok finally got it to work. Hope this helps someone else. After doing lots of digging.
</p><p>"You'll have to open it through a terminal: firefox -p "profile name" --allow-downgrade."
</p>Now im worse off im back to ver 76 but can't get FF to load or start or create new profile and cant 2020-06-08T13:37:50-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1321842<p>Now im worse off im back to ver 76 but can't get FF to load or start or create new profile and cant change to a different profile listed.
I click on FF icon to open and start, now it pops up to create new profile, or exit I do not want to create a new profile every time I start FF. forced to create another profile in order to get to about:profile to try and set the default profile.
</p>Will test some more tomorrow. now back to ver 76, but now how do I set default back to the profile I2020-06-08T13:12:21-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1321835<p>Will test some more tomorrow. now back to ver 76, but now how do I set default back to the profile I want. it keeps say you've launched an older ver of ff, to exit or create new profile, i want to start a specif profile and stick to it . using profile manger
</p>Is multi-process still disabled if you check this on about:support ?
Are there accessibility se2020-06-08T13:04:01-07:00cor-elhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1321832<p>Is multi-process still disabled if you check this on about:support&nbsp;?
</p><p>Are there accessibility services active as reported on about:support&nbsp;?
</p>
<ul><li><a href="https://support.mozilla.org/en-US/kb/accessibility-services" rel="nofollow">https://support.mozilla.org/en-US/kb/accessibility-services</a>
</li></ul>No MOZ_FORCE_DISABLE_E10S environment triple checked.
Created TEST new profile and set to start with2020-06-08T12:19:46-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1321820<p>No MOZ_FORCE_DISABLE_E10S environment triple checked.
</p><p>Created TEST new profile and set to start with new,
rename pref.js to prefOLD.js
</p><p><br>
Now it's intermittent. some pages load ok, but then hyperlinks don't work, right click new tab and get garbage.
</p><p>Seems ok for while on <a href="http://mozzila.org" rel="nofollow">mozzila.org</a> site then start to get garbage.
</p>Are you sure you removed the MOZ_FORCE_DISABLE_E10S environment because MOZ_FORCE_DISABLE_E10S=0 won2020-06-08T12:00:00-07:00cor-elhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1321818<p>Are you sure you removed the <b>MOZ_FORCE_DISABLE_E10S</b> environment because MOZ_FORCE_DISABLE_E10S=0 won't work (merely its presence is sufficient)&nbsp;?
</p><p>If that is the case then try to rename prefs.js in the profile folder (prefsOLD.js).
</p><p>You can use the button on the "Help -&gt; Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the <b>about:profiles</b> page.
</p>
<ul><li>Help -&gt; Troubleshooting Information -&gt; Profile Folder/Directory:<br>Windows: Open Folder; Linux: Open Directory; Mac: Show in Finder
</li><li><a href="https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data" rel="nofollow">https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data</a>
</li></ul>This doesn't seem right.
Multi process Windows = 0/1Disabled forcibly
Remote Process = 0
While my 2020-06-08T11:48:04-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589?page=2#answer-1321816<p>This doesn't seem right.
</p><p>Multi process Windows = 0/1Disabled forcibly
</p><p>Remote Process = 0
</p><p>While my laptop shows:
</p><p>Multi process Windows = 1/1 Enabled by default
</p><p>Remote Process = 8
</p>That was too hard to read;
Launcher process = Enabled
Multi process Windows = 0/1
Disabled forcibl2020-06-08T11:43:22-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589#answer-1321815<p>That was too hard to read;
</p><p>Launcher process = Enabled
</p><p>Multi process Windows = 0/1
</p><p>Disabled forcibly Remote Process = 0
</p>States:
Launcher process = Enabled
Multi process Windows = 0/1 Disabled forcibly
Remote Process = 0
2020-06-08T11:40:41-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589#answer-1321813<p>States:
</p><p>Launcher process = Enabled
Multi process Windows = 0/1 Disabled forcibly
Remote Process = 0
</p><p>Now checking into profiles
</p>You can find the current multi-process state on the Troubleshooting Information page (about:support)2020-06-08T11:24:07-07:00cor-elhttps://support.mozilla.org/zu/questions/1289589#answer-1321808<p>You can find the current multi-process state on the Troubleshooting Information page (about:support).
</p>
<ul><li>"Help -&gt; Troubleshooting Information" -&gt; "Application Basics":<br>Multiprocess Windows<br>Remote Processes
</li></ul>
<p>See also the Remote Processes section further down for more detail.
</p>
<hr>
<p>You can delete possible user.js and numbered prefs#-##.js files and rename/remove the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in current Firefox releases.
</p><p>You can use the button on the "Help -&gt; Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the <b>about:profiles</b> page.
</p>
<ul><li>Help -&gt; Troubleshooting Information -&gt; Profile Folder/Directory:<br>Windows: Open Folder; Linux: Open Directory; Mac: Show in Finder
</li><li><a href="https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data" rel="nofollow">https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data</a>
</li></ul>
<hr>
<p>You can create a new profile as a quick test to see if your current profile is causing the problem.
</p><p>See "Creating a profile":
</p>
<ul><li><a href="https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles" rel="nofollow">https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles</a>
</li></ul>
<p>If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
</p>
<ul><li><a href="https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile" rel="nofollow">https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile</a>
</li></ul>Just noticed on Brian's original question he says "my system was low on resources so it killed the p2020-06-08T11:22:15-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589#answer-1321804<p>Just noticed on Brian's original question he says "my system was low on resources so it killed the process using the most memory which was Firefox."
</p><p>On mine I was not involved with any resources or processes at the time, it was only a usual auto FF upgrade it happened to be to ver 77.
</p><p>should maybe start a new tread?
</p>Wanted to try one last time. I downgraded to ver 76 was using for a few days works fine, upgrade to 2020-06-08T11:06:35-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589#answer-1321800<p>Wanted to try one last time. I downgraded to ver 76 was using for a few days works fine, upgrade to ver 77 as a test and back to on screen garbage text.
</p><p>Tried changing browser.tabs.remote.autostart set to true or false neither made any difference.
</p><p>Unless anyone else has any new ideas to test I think for now I will have to settle for ver 76 and keep using FF that way. I've been using it on the same desktop for years with no problems, only now with the new auto upgrade to ver 76.
</p><p>Could it be a rare bug?
</p>At the moment I've gone back to ver 76 due to my work and its stable. Just tried for both true and f2020-06-07T11:20:16-07:00tradepenhttps://support.mozilla.org/zu/questions/1289589#answer-1321370<p>At the moment I've gone back to ver 76 due to my work and its stable. Just tried for both true and false re browser.tabs.remote.autostart in about:config and there was no change. Tomorrow I will try going back to ver 77 and try this possible solution. Will report back at that time.
</p><p>Any other options not already posted and tried would be appreciated.
</p><p>Thanks
</p>I still see browser.tabs.remote.autostart as a pref in about:config, but I don't know what effect th2020-06-05T17:04:48-07:00cor-elhttps://support.mozilla.org/zu/questions/1289589#answer-1320427<p>I still see browser.tabs.remote.autostart as a pref in about:config, but I don't know what effect this pref has and best is to keep it true.
</p>cor-el said
The browser.tabs.remote.autostart pref needs to be true to enable multi-process, becaus2020-06-05T16:11:27-07:00brian119https://support.mozilla.org/zu/questions/1289589#answer-1320407<em><p>cor-el <a href="#answer-1320403" rel="nofollow">said</a></p></em>
<blockquote>
The <b>browser.tabs.remote.autostart</b> pref needs to be <em>true</em> to enable multi-process, because disabling multi-process is causing this issue.
</blockquote>
<p>That's odd. I have browser.tabs.remote.autostart=false and multi-process is working just fine.
</p>The browser.tabs.remote.autostart pref needs to be true to enable multi-process, because disabling m2020-06-05T15:59:04-07:00cor-elhttps://support.mozilla.org/zu/questions/1289589#answer-1320403<p>The <b>browser.tabs.remote.autostart</b> pref needs to be <em>true</em> to enable multi-process, because disabling multi-process is causing this issue.
</p>