Bugzilla

(In reply to Haik Aftandilian [:haik] from comment #4)
> (In reply to Darkspirit from comment #3)
> > Naive question: Does MacOS need to differ from Linux?
> 
> To clarify the question, do you mean to ask if Linux should also adopt this change (bug 1827747) [...]

Yes - at the time of writing my comment. (I'm not a developer, just a user/tester).
Sorry, I was confused about this MacOS special casing and the meaning of plugin-container.
I was not aware
* that Linux' firefox-bin and Mac's new gmp process also just contain plugin-container,
* that Mac can't use firefox-bin for content processes as it would cause a Dock icon per content process (bug 1827486 comment 24).

Now I have found bug 1532782 which is about removing the plugin-container binary from Linux. Currently it's only used for GMP.
bug 1470591/bug 1609882 (dom.ipc.forkserver.enable) would fix the about:restartrequired problem on Linux and allegedly also speed up content process launches. (Should it therefore also be enabled on macOS and could browser.tabs.remote.warmup.enabled be disabled then? Shouldn't it also cover utility/socket/webextension/privileged processes and maybe even GMP?)

Linux:
  * current default:
    * firefox-bin as main process
      * firefox-bin as content/socket/utility/webextension/privileged processes
      * plugin-container as GMP process
  * with manually enabled dom.ipc.forkserver.enable (bug 1470591/bug 1609882):
    * firefox-bin as main process
      * firefox-bin as forkserver
        * firefox-bin as content processes
          (socket/utility/webextension/privileged/GMP are not below forkserver - should they? Do they currently fail to re-launch in case firefox-bin has been replaced?)
      * firefox-bin as socket/utility/webextension/privilege process
      * plugin-container as GMP process

(In reply to Haik Aftandilian [:haik] from comment #4)
> (In reply to Darkspirit from comment #3)
> > Naive question: Does MacOS need to differ from Linux?
> 
> To clarify the question, do you mean to ask if Linux should also adopt this change (bug 1827747) [...]

Yes - at the time of writing my comment. (I'm not a developer, just a user/tester).
Sorry, I was confused about this MacOS special casing and the meaning of plugin-container.
I was not aware
* that Linux' firefox-bin and Mac's new gmp process also just contain plugin-container,
* that Mac can't use firefox-bin for content processes as it would cause a Dock icon per content process (bug 1827486 comment 24).

Now I have found bug 1532782 which is about removing the plugin-container binary from Linux. Currently it's only used for GMP.
bug 1470591/bug 1609882 (dom.ipc.forkserver.enable) would fix the about:restartrequired problem on Linux and allegedly also speed up content process launches. (Should it therefore also be enabled on macOS and could browser.tabs.remote.warmup.enabled be disabled then? Shouldn't it also cover utility/socket/webextension/privileged processes and maybe even GMP?)

Linux:
  * current default:
    * firefox-bin as main process
      * firefox-bin as content/socket/utility/privileged processes
      * plugin-container as GMP process
  * with manually enabled dom.ipc.forkserver.enable (bug 1470591/bug 1609882):
    * firefox-bin as main process
      * firefox-bin as forkserver
        * firefox-bin as content/webextension processes
          (socket/utility/privileged/GMP are not below forkserver - should they? Do they currently fail to re-launch in case firefox-bin has been replaced?)
      * firefox-bin as socket/utility/webextension/privilege process
      * plugin-container as GMP process

(In reply to Haik Aftandilian [:haik] from comment #4)
> (In reply to Darkspirit from comment #3)
> > Naive question: Does MacOS need to differ from Linux?
> 
> To clarify the question, do you mean to ask if Linux should also adopt this change (bug 1827747) [...]

Yes - at the time of writing my comment. (I'm not a developer, just a user/tester).
Sorry, I was confused about this MacOS special casing and the meaning of plugin-container.
I was not aware
* that Linux' firefox-bin and Mac's new gmp process also just contain plugin-container,
* that Mac can't use firefox-bin for content processes as it would cause a Dock icon per content process (bug 1827486 comment 24).

Now I have found bug 1532782 which is about removing the plugin-container binary from Linux. Currently it's only used for GMP.
bug 1470591/bug 1609882 (dom.ipc.forkserver.enable) would fix the about:restartrequired problem on Linux and allegedly also speed up content process launches. (Should it therefore also be enabled on macOS and could browser.tabs.remote.warmup.enabled be disabled then? Shouldn't it also cover utility/socket/privileged processes and maybe even GMP?)

Linux:
  * current default:
    * firefox-bin as main process
      * firefox-bin as content/socket/utility/privileged processes
      * plugin-container as GMP process
  * with manually enabled dom.ipc.forkserver.enable (bug 1470591/bug 1609882):
    * firefox-bin as main process
      * firefox-bin as forkserver
        * firefox-bin as content/webextension processes
          (socket/utility/privileged/GMP are not below forkserver - should they? Do they currently fail to re-launch in case firefox-bin has been replaced?)
      * firefox-bin as socket/utility/webextension/privilege process
      * plugin-container as GMP process

(In reply to Haik Aftandilian [:haik] from comment #4)
> (In reply to Darkspirit from comment #3)
> > Naive question: Does MacOS need to differ from Linux?
> 
> To clarify the question, do you mean to ask if Linux should also adopt this change (bug 1827747) [...]

Yes - at the time of writing my comment. (I'm not a developer, just a user/tester).
Sorry, I was confused about this MacOS special casing and the meaning of plugin-container.
I was not aware
* that Linux' firefox-bin and Mac's new gmp process also just contain plugin-container,
* that Mac can't use firefox-bin for content processes as it would cause a Dock icon per content process (bug 1827486 comment 24).

Now I have found bug 1532782 which is about removing the plugin-container binary from Linux. Currently it's only used for GMP.
bug 1470591/bug 1609882 (dom.ipc.forkserver.enable) would fix the about:restartrequired problem on Linux and allegedly also speed up content process launches. (Should it therefore also be enabled on macOS and could browser.tabs.remote.warmup.enabled be disabled then? Shouldn't it also cover RDD/utility/socket processes and maybe even GMP?)

Linux:
  * current default:
    * firefox-bin as main process
      * firefox-bin as content/RDD/socket/utility/webextension/privileged processes
      * plugin-container as GMP process
  * with manually enabled dom.ipc.forkserver.enable (bug 1470591/bug 1609882):
    * firefox-bin as main process
      * firefox-bin as forkserver
        * firefox-bin as content/webextension/privileged processes
          (RDD/socket/utility/GMP are not below forkserver - should they? Do they currently fail to re-launch in case firefox-bin has been replaced?)
      * firefox-bin as socket/utility process
      * plugin-container as GMP process