In GV we have `dom.ipc.keepProcessesAlive.web` set to `1`. While this does indeed keep the process around, under e10s-multi, that retained process never gets reused until the number of live content processes reaches the maximum. If we do something like this in GV: ``` geckoSession1.open(...); // Create first content process geckoSession1.close(); // First content process is kept around because of keepProcessesAlive geckoSession2.open(...); // But we're not yet at the maximum, so instead of reusing that first process, we create a second one ``` We end up with *two* content processes even though one would have sufficed, and we don't get the perf benefits of reusing an existing process.
Bug 1647470 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In GV we have `dom.ipc.keepProcessesAlive.web` set to `1`. While this does indeed keep the process around, under e10s-multi, that retained process never gets reused until the number of live content processes reaches the maximum. If we do something like this in GV: ``` geckoSession1.open(...); // Create first content process geckoSession1.close(); // First content process is kept around because of keepProcessesAlive geckoSession2.open(...); // But we're not yet at the maximum, so instead of reusing that first process, we create a second one ``` We end up with *two* content processes even though one would have sufficed, and we don't get the perf benefits of reusing an existing process. This is particularly egregious on mobile due to Android process termination etc.