Setting "dom.ipc.processCount" resets itself to 1?
As written, with Ff 89 beta for Android, the setting "dom.ipc.processCount" resets itself to 1 every restart.
https://github.com/mozilla-mobile/fenix/issues/19385
Can someone please explain me why? It felt much faster before with a setting of 4 or 6 and still feels faster when I set it in about:config for the time not doing a restart...what is going on here?
And why is such a change not being communicated to the community somehow and I/we have to find this out by ourself?
Greets and with best regards, Michael
Alle svar (8)
Hi
This is a process that is managed in GeckoView and is not configurable through about:config.
Ok, and why am I being able to set "dom.ipc.processCount" in Ff 88's prefs.js or about:config successful to 6, resulting in up to 6 webcontent-processes shown in "about:support" - and not in 89 anymore?
Or: why uses Ff 89 less WebContent-processes (and feels slower...) than Ff 88?
Ændret af Msteam1 den
@Seburo ?
Why am I being able to set "dom.ipc.processCount" in Ff 88's prefs.js or about:config successful to 6, resulting in up to 6 webcontent-processes shown in "about:support" - and not in 89 anymore?
Or: why uses Ff 89 less WebContent-processes (and feels slower...) than Ff 88?
? I am still waiting for an answer
Hi
It looks like this issue has already been flagged up to our developers. You can follow progress on this at:
@Seburo Really? This is the report I have sent to you - my report I have opened
Msteam1 said
As written, with Ff 89 beta for Android, the setting "dom.ipc.processCount" resets itself to 1 every restart. https://github.com/mozilla-mobile/fenix/issues/19385 Can someone please explain me why?
Because this commit has landed on 89: https://phabricator.services.mozilla.com/D109798 . It resets the setting "dom.ipc.processCount" to 1 (in 90 to 2) every restart.
I believe that everything is explained right now.
This parameter is locked to 1 after a certain update. You can customize the size of the value, but the value will be reset to 1 after closing the software and opening the software again. Not only this value is locked, but many other parameters are locked, such as "browser.safebrowsing.malware.enabled" and "browser.safebrowsing.phishing.enabled". These values can be unlocked by recompiling.