Bugzilla

Jumping to random (and maybe wrong) conclusions ("freeze", "performance") without any references does not help.

> I saw that the main firefox process has opened about 150 (!!!) sub-processess, with al together "eat up" a lot of system resources (one of the sub-processes, with it's each sub-process "eat" ca. 26.4 G of virtual memory)

If there was only 1 sub-process which took 26.4 G of memory, how would that change anything?

> the main process should open ** only one ** sub-process for each window, tab, addon or multimedia (audio, video, flash) content

There is no reason to change the architecture if there is no explanation or proof if that would solve any perceived problem.

This ticket is jumping to conclusions, so I consider this ticket neither useful nor actionable.

If you run into memory issues, then please enter the address
   about:memory?verbose
in the address bar and attach (using the "Attach New File" link above) the output here.

Jumping to random (and maybe wrong) conclusions ("freeze", "performance") without any references does not help.

> I saw that the main firefox process has opened about 150 (!!!) sub-processess, with al together "eat up" a lot of system resources (one of the sub-processes, with it's each sub-process "eat" ca. 26.4 G of virtual memory)

If there was only 1 sub-process which took 26.4 G of memory, how would that change anything?

> the main process should open ** only one ** sub-process for each window, tab, addon or multimedia (audio, video, flash) content

There is no reason to change the architecture when there is no explanation or proof that it would solve any perceived problem.

This ticket is jumping to random conclusions, so I consider this ticket neither useful nor actionable.

If you run into memory issues, then please enter the address
   about:memory?verbose
in the address bar and attach (using the "Attach New File" link above) the output here.