>I haven't enabled it... it was automatically starting up with Firefox Can you go to about:config and look for: dom.ipc.forkserver.enable and tell us the value? The screenshot you posted on the support page indeed seems to be consistent with the forkserver somehow being enabled. >First, Please stop changing the "component" of the bug report because it's NOT a DCOM but Performance issue (violation of the "Changing fields" rule point 1.). People are changing the component because "Performance" is very generic and we want to identify which *actual component* is causing the unexpected behavior. DOM:Content Processes is responsible for launching additional processes to load web content. It's not 100% clear that is the cause here, but someone who knows that module might have more info (if they were able to look at it...which is hard if the bugs keeps getting moved to the generic component). >sub-processess, I mean the ones with are opened from an main process From your image, you mean both processes and threads. It's normal for Firefox to have a lot of threads, this is expected for optimal performance. We also expect a lot of processes (even more in newer versions), but your screenshot has a bunch of a type we don't expect.
Bug 1687376 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>I haven't enabled it... it was automatically starting up with Firefox Can you go to about:config and look for: dom.ipc.forkserver.enable and tell us the value? The screenshot you posted on the support page indeed seems to be consistent with the forkserver somehow being enabled. >First, Please stop changing the "component" of the bug report because it's NOT a DCOM but Performance issue (violation of the "Changing fields" rule point 1.). People are changing the component because "Performance" is very generic and we want to identify which *actual component* is causing the unexpected behavior. DOM:Content Processes is responsible for launching additional processes to load web content. It's not 100% clear that is the cause here, but someone who knows that module might have more info (if they were able to look at it...which is hard if the bugs keeps getting moved to the generic component). >sub-processess, I mean the ones with are opened from an main process From your image, you mean both processes and threads. It's normal for Firefox to have a lot of threads, this is expected for optimal performance and entails minimal memory overhead for reasons already explained in this bug. We also expect a lot of processes (even more in newer versions), but your screenshot has a bunch of a type we don't expect.
>I haven't enabled it... it was automatically starting up with Firefox Can you go to about:config and look for: dom.ipc.forkserver.enable and tell us the value? The screenshot you posted on the support page indeed seems to be consistent with the forkserver somehow being enabled. >First, Please stop changing the "component" of the bug report because it's NOT a DCOM but Performance issue (violation of the "Changing fields" rule point 1.). People are changing the component because "Performance" is very generic and we want to identify which *actual component* is causing the unexpected behavior. DOM:Content Processes is responsible for launching additional processes to load web content. It's not 100% clear that is the root cause here, but someone who knows that module might have more info (if they were able to look at it...which is hard if the bugs keeps getting moved to the generic component). >sub-processess, I mean the ones with are opened from an main process From your image, you mean both processes and threads. It's normal for Firefox to have a lot of threads, this is expected for optimal performance and entails minimal memory overhead for reasons already explained in this bug. We also expect a lot of processes (even more in newer versions), but your screenshot has a bunch of a type we don't expect.