Improve non-e10s mode #82
Comments
K4sum1
added
enhancement
|
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. |
|
So for this bug #83 It seems the browser just doesn't go in full screen video mode. It acts like you just pressed F11 to but the browser in a basic full screen mode, but it's not video full screen. 70 is the last release to work, so I assume testing nightly builds between 70 and 71 would be the way to find the cause here. |
|
So for this bug #84 Some about pages are broken, specifically about:logisn and about:newtab. about:logins seems to require e10s, specifically the privileged about process to work. Maybe it could be somehow made to work in single process mode, but the easiest way would be to bring back the classic separate logins window like in 68. about:newtab works at first launch, but then just breaks if you open it again. 71 is the last to have consistently working about:newtab. 67 did not have an about:logins. 68/69 it refuses to load, 70 it's as broken as current version. No idea if any other pages are broken. |
|
So for this bug #106 Phantom tabs is an annoying issue that I would love to have fixed. They can happen with or without e10s, however it seems Mozilla did actually fix this pretty well (at least with e10s) and I can't remember the last time I dealt with this (when using e10s). However when not using e10s, you will always have a phantom tab. Just start the browser, open a new tab, and close the tab the browser started with. It will stay in the tab bar, but otherwise be closed, unable to be switched to or anything. Just wasting space in the tab bar until the browser is closed. 102 ESR does not have the issue in non-e10s. However I believe the issue can still happen. This isn't the root cause of the phantom tab issue completely, but probably good enough as I don't know how or why or have any hope of me being able to figure out why this even happens in the first place. Also the toolbar is funny in general with no e10s, like for example the glow for opening a tab off screen or outside of the bar does not appear anymore, and if you scroll and open a new tab, it does not scroll back to where the tab opens or the active tab. Not sure where this began, will have to test it. |
|
So for this bug #108 So it's just very slow, much slower than it should be. |
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.
The text was updated successfully, but these errors were encountered: