Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

High number of processes for Firefox 102.0.1esr with only one tab; How to reduce

more options

Hi,

I am testing v102esr of Firefox for a rollout in September.

One of this issues I have come across is the extremely high number of processes started when opening Firefox.

We have our own website run via Windows Server using IIS. The home page has no remote content - it's all local so I don't believe any remote content is being opened. There is only one tab open.

For each new tab I open I get at least one additional process. So with 10 tabs opened I ended up with 24 processes.

In FF91esr this was 3-5 processes. I also noticed under performance settings I can no longer specify the number of processes.

Is there any way to reduce this number to something more sane, like 3-5?

Also, why is there a Console Window Host running under Firefox?

Is the Node.js also new? I don't recall seeing it before

thanks

Hi, I am testing v102esr of Firefox for a rollout in September. One of this issues I have come across is the extremely high number of processes started when opening Firefox. We have our own website run via Windows Server using IIS. The home page has no remote content - it's all local so I don't believe any remote content is being opened. There is only one tab open. For each new tab I open I get at least one additional process. So with 10 tabs opened I ended up with 24 processes. In FF91esr this was 3-5 processes. I also noticed under performance settings I can no longer specify the number of processes. Is there any way to reduce this number to something more sane, like 3-5? Also, why is there a Console Window Host running under Firefox? Is the Node.js also new? I don't recall seeing it before thanks
Attached screenshots

Chosen solution

Those changes to processes are a result of the fission experiment (see link below). You can opt out by changing the following preference to false. fission.autostart You need to restart the browser for the change to take effect.

https://wiki.mozilla.org/Project_Fission

Can you dismiss the "Windows Console Host"? If not, can you provide a screenshot?

Read this answer in context 👍 1

All Replies (2)

more options

Chosen Solution

Those changes to processes are a result of the fission experiment (see link below). You can opt out by changing the following preference to false. fission.autostart You need to restart the browser for the change to take effect.

https://wiki.mozilla.org/Project_Fission

Can you dismiss the "Windows Console Host"? If not, can you provide a screenshot?

Helpful?

more options

I can "kill" the console host process, but I shouldn't have to do that.

Anyway, setting the fission.autostart preference to false restores Firefox to a more sane 4 processes.

Sir, you are a legend. Thank you!

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.