Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.
Multiprocess can't be stopped via about:config. Why not?
Latest version of FF 68.0 has re-enabled multiprocess and won't allow me to disable via about:config.
I've been with FF since pretty much the beginning, it's the only browser I recommend to friends, family or clients. Since 10e and the whole multiprocess roll out, I've "fixed" peoples slow and unresponsive FF experience by disabling this useless feature and H/W acceleration.
Now my mailbox is full of complaints about slow unresponsive browsing, plus it using more system resources leaving clients with less powerful machines with real problems.
C'mon Moz, we've been mates for decades, stood by you when everyone was looking at whatever MS was waiving at them, laughed at Google when they tried to play with the big boy, but now I'm feeling sheepish about my claims of Mozilla putting its users needs first, not forcing features on users, giving its users a choice enabling a freedom that you don't have with Edge or Chrome
Please give us back one of the remaining freedoms we have left, don't be MICROSOFT!
Alle svar (2)
You can no longer do this via about:config, but you need to set an environment variable to disable multi-process.
- set MOZ_FORCE_DISABLE_E10S=1
Ændret af cor-el den