We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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

Video DownloadHelper with companion app uses only one Firefox sub-process.

  • 21 majibu
  • 1 ana tatizo hili
  • 1 view
  • Last reply by hanaana

more options

I am using Video Download Helper with companion app, when downloading videos, the DownloadHelper will uses only one process of Firefox with very high CPU and memory usage. . Ans cause it does not take advantage of all the CPU cores it is very slow, and uses high memory for that process and will make all tabs in Firefox slow.

It seems that this process is the core process for Firefox, although it is a sub-process. It is the process that almost doesn't uses GPU memory.

When finished, if I killed this Firefox process to clean memory, cause it will just accumulate the memory in that specific process, all the tabs in the Firefox will crash and can't be refreshed, until I close Firefox and open it again.

Usually when I kill a Firefox process that is not responding, it will crash a few tabs and they can be refreshed after that.

Is there anyway that can make the companion app uses all processes for Firefox, so it will distribute the CPU usage to all cores, and if used a high memory it will be distribute the memory to all process and will be easier to clean.

I am using Video Download Helper with companion app, when downloading videos, the DownloadHelper will uses only one process of Firefox with very high CPU and memory usage. . Ans cause it does not take advantage of all the CPU cores it is very slow, and uses high memory for that process and will make all tabs in Firefox slow. It seems that this process is the core process for Firefox, although it is a sub-process. It is the process that almost doesn't uses GPU memory. When finished, if I killed this Firefox process to clean memory, cause it will just accumulate the memory in that specific process, all the tabs in the Firefox will crash and can't be refreshed, until I close Firefox and open it again. Usually when I kill a Firefox process that is not responding, it will crash a few tabs and they can be refreshed after that. Is there anyway that can make the companion app uses all processes for Firefox, so it will distribute the CPU usage to all cores, and if used a high memory it will be distribute the memory to all process and will be easier to clean.

Chosen solution

I can confirm, test with Firefox 70 beta 1 and problem was fixed!

Read this answer in context 👍 0

All Replies (1)

more options

Suluhisho teule

I can confirm, test with Firefox 70 beta 1 and problem was fixed!

  1. 1
  2. 2