Open K4sum1 opened 3 months ago
Interesting bug. I guess another thing I will have go looking for when trying to remove the other processes. Confirmed on my machine.
Although I want to focus on other projects for a bit.
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, 70 is the last to work.
Originally posted by @jonm58 in https://github.com/Eclipse-Community/r3dfox/issues/9#issuecomment-2170850894