K4sum1
commented
2 months ago If you want to help, there is a way to figure out the potential cause of the issue.
The newest stock Firefox nightly that can disable e10s with the environment variable at least on a consumer machine is a 123 alpha from 2024/01/21 I think. However all of these are still an issue with the 115 ESR release, so it doesn't really matter here.
Between 81 and 123, MOZ_FORCE_DISABLE_E10S needs to be set to the application version to take effect. I'm not sure if this includes the a1 or .x.x or whatever. I assume it would though. https://hg.mozilla.org/mozilla-central/rev/13171155d5e5
Before 81 and any 81 alpha builds before the commit, it just needs to be set to 1.
Using this information, if you can find the nightly builds that cause the issues and report back here with the last to work and the first to have the issue, I would really appreciate it.
I assume the progression would be find first working ESR, then first working release, and then first working nightly.
I'll help narrow it down, 102 ESR seems to only have the socket process with e10s disabled, so two processes. 91 ESR has only one single browser process.
Edit: The socket process can be disabled by setting network.process.enabled to false. Not sure if I can assign multiple commands to a single option, but I guess I'll see if I can. These might also do stuff, not sure. Might need to fix some like privileged about doing nothing. https://old.reddit.com/r/firefox/comments/cc8bdm/multiprocess_wont_disable_via_aboutconfig/etl5zyc/
With the option enabled, it seems it runs in the non-e10s or single browser and content process mode, however there are still other remote processes that need to be disabled. I guess I can either look into them, ask in Firefox chats, or dig through nightly builds with the weird environment variable method to figure out where they come from and how to disable them.