Video DownloadHelper with companion app uses only one Firefox sub-process.
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.
Solution choisie
I can confirm, test with Firefox 70 beta 1 and problem was fixed!
Lire cette réponse dans son contexte 👍 0Toutes les réponses (20)
As this problem is with Video Download Helper (which one, there are several with that name) you should contact their support.
FredMcD said
As this problem is with Video Download Helper (which one, there are several with that name) you should contact their support.
It doesn't concern this specific add-on, but it is about how Firefox manages and runs add-ons.
1- Firefox uses only one sub-process to run add-ons. Solution:Multi.core programming for this process, or distributing new threads to new processes.
2- Firefox doesn't clean memory when done. During downloading videos, sometimes this specific process uses 10 GB Ram, and Firefox doesn't empty or clean the memory when done even though the app is closed and the add-on is not running anymore, even disabling the add-on will not help. Solution: Firefox should check and clean memory used by add-ons.
It is a Firefox problem!
Modifié le par hanaana
Next time you see high memory usage after completed activity, could you test the buttons in the "Free memory" section of this page to see whether they clean up that process?
about:memory
Also, if you don't normally show the Command Line column in the Details tab of the Windows 10 Task Manager, you might try that. It should better distinguish the processes.
jscher2000 said
Next time you see high memory usage after completed activity, could you test the buttons in the "Free memory" section of this page to see whether they clean up that process? about:memory Also, if you don't normally show the Command Line column in the Details tab of the Windows 10 Task Manager, you might try that. It should better distinguish the processes.
I am not being clear? it is a Firefox process Firefox.exe
And thanks for the advise about clean memory, I used to use it but it doesn't help. And since Firefox 66 it is useless cause Firefox clear the memory automatically as I noticed and that Firefox uses more sub-process which is nice.
I Uploaded an images to show which process, now it is using almost 3 GB, and they will not be cleared when finished
Modifié le par hanaana
jscher2000 said
Next time you see high memory usage after completed activity, could you test the buttons in the "Free memory" section of this page to see whether they clean up that process? about:memory Also, if you don't normally show the Command Line column in the Details tab of the Windows 10 Task Manager, you might try that. It should better distinguish the processes.
I downloaded few more videos, maybe 2 or 3 and not it is 4.5 GB and nope they will not be cleared.
You can check the about:memory page for the Firefox memory usage and possible click the button to minimize memory usage.
cor-el said
You can check the about:memory page for the Firefox memory usage and possible click the button to minimize memory usage.
I already know about it, about:memory and I clear GC, CC, minmize memory usage.
They wont help that specific process. Only that process will not be cleared.
Soon I will upload an image to show how it will be 10GB
cor-el said
You can check the about:memory page for the Firefox memory usage and possible click the button to minimize memory usage.
And killing that process, will cause all the tabs to crash, and they wont be refreshed.
Usually killing any other Firefox.exe will cause few tab to crash and they CAN be refreshed after.
If you check the image, it uses the least GPU memory. It maybe a process to manage and run add-ons!
Modifié le par hanaana
hanaana said
I am not being clear? it is a Firefox process Firefox.exe
My comment will make more sense if you add the Command Line column to your Details view in the Windows Task Manager. You should be able to cross-reference the PID with the tool you're using. But it's just a matter of curiosity. Someone may need to debug the extension to understand why it doesn't let Firefox release memory when you close the relevant tab.
jscher2000 said
hanaana saidI am not being clear? it is a Firefox process Firefox.exeMy comment will make more sense if you add the Command Line column to your Details view in the Windows Task Manager. You should be able to cross-reference the PID with the tool you're using. But it's just a matter of curiosity. Someone may need to debug the extension to understand why it doesn't let Firefox release memory when you close the relevant tab.
Maybe I should have mentioned that is problem is new! I have always used that download helper and it worked just fine.
I can't remember, but since Firefox 64 maybe 63 or even 62, or let's say it is a new problem. the problem began to occur.
The problem was not happening before, with the same version of that extension. cause it was not updated for a long time
jscher2000 said
hanaana saidI am not being clear? it is a Firefox process Firefox.exeMy comment will make more sense if you add the Command Line column to your Details view in the Windows Task Manager. You should be able to cross-reference the PID with the tool you're using. But it's just a matter of curiosity. Someone may need to debug the extension to understand why it doesn't let Firefox release memory when you close the relevant tab.
Sorry Yesterday I felt asleep,
Here is the command line, not sure if it is gonna help
"C:\Program Files\Mozilla Firefox\firefox.exe" -contentproc --channel="10784.20.1714415784\752715038" -childID 3 -isForBrowser -prefsHandle 3920 -prefMapHandle 3924 -prefsLen 6061 -prefMapSize 195517 -parentBuildID 20190404130536 -greomni "C:\Program Files\Mozilla Firefox\omni.ja" -appomni "C:\Program Files\Mozilla Firefox\browser\omni.ja" -appdir "C:\Program Files\Mozilla Firefox\browser" - 10784 "\\.\pipe\gecko-crash-server-pipe.10784" 3932 tab
Attaching a new pic, showing how it is.
If someone is a pro here and reading, it is not about downloadhelper, even when I use "Dark Reader" add-on I notice after a wile it will slow the browser.
It is how Firefox manages add-ons, I think Firefox fails to clear memory for add-ons in general,
Boot the computer in Windows Safe mode with network support to see if that has effect in case security software is causing problems.
- http://www.bleepingcomputer.com/tutorials/how-to-start-windows-in-safe-mode/
- http://www.7tutorials.com/4-ways-boot-safe-mode-windows-10
You can try to disable hardware acceleration in Firefox.
- Options/Preferences -> General: Performance
remove checkmark: [ ] "Use recommended performance settings"
remove checkmark: [ ] "Use hardware acceleration when available" - https://support.mozilla.org/en-US/kb/performance-settings
Close and restart Firefox after modifying the setting for changes to take effect.
You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.
cor-el said
Boot the computer in Windows Safe mode with network support to see if that has effect in case security software is causing problems.You can try to disable hardware acceleration in Firefox.
- http://www.bleepingcomputer.com/tutorials/how-to-start-windows-in-safe-mode/
- http://www.7tutorials.com/4-ways-boot-safe-mode-windows-10
Close and restart Firefox after modifying the setting for changes to take effect. You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.
- Options/Preferences -> General: Performance
remove checkmark: [ ] "Use recommended performance settings"
remove checkmark: [ ] "Use hardware acceleration when available"- https://support.mozilla.org/en-US/kb/performance-settings
Nope, it is not hardware acceleration issue nor antivirus
jscher2000 said
hanaana saidI am not being clear? it is a Firefox process Firefox.exeMy comment will make more sense if you add the Command Line column to your Details view in the Windows Task Manager. You should be able to cross-reference the PID with the tool you're using. But it's just a matter of curiosity. Someone may need to debug the extension to understand why it doesn't let Firefox release memory when you close the relevant tab.
Today I wanted to show you the 10GB even though I disabled the add-on, but the moment I disable the download helper add-on the 10GB memory went down to 200MB
you were right, it is something about Firefox and this add-on maybe.
Here is the link fir the add-on https://addons.mozilla.org/en-US/firefox/addon/video-downloadhelper/
Last updated 8 months ago (Aug 1, 2018)
I suggest you contact its support as Firefox has gone thru several reversions in the last 8 months.
FredMcD said
Last updated 8 months ago (Aug 1, 2018) I suggest you contact its support as Firefox has gone thru several reversions in the last 8 months.
I updated today to 67 beta 9 and problem solved!
Coincidence? i think not!
It was a Firefox bug!
I will return for sure, but I tested downloading lots of files, Firefox used almost 3GB RAM, and when done downloading the memory went done to 400MB and that was something new!
Modifié le par hanaana
Confirmed! Firefox 67 Beta 9 fixes the problem!
Not only that, I have even noticed using the dark reader add-on will not slow down the browsing as it used to be!
It was a Firefox bug and the latest beta 9 fixes it.
Modifié le par hanaana
That was very good work. Well done.
The question who did it? I did report and linked this thread, did they had the time to fix it? did they had the time to read my thread?
That was strange unless it was reported before!
All the add-ons seem to work faster now, although they use only one Firefox process. If only Mozilla will consider making this process, which is responsible for running add-ons, multi core programmed,
But for now it is much much better.
I am gonna leave this open again.
Absolutely there is improvement but not completely fixed.
After a while now, Firefox is using almost 1GB RAM, disabling the add/on went back to 350MB
usually around this point Firefox will be 3GB if not more, but around 1GB there is improvement.