Not sure if it occurs in Windows' version of firefox. I wonder if the developer can add some sleeps to his code that would avoid the extension from constantly spinning its wheels. It isn't a huge problem, but sometimes the extra cpu utilization is just enough to kick in the cpu cooling fans, which are annoying to listen to. The cpu utilization drops to near-zero the moment I disable this extension. The issue can be seen from the operating system level. A Native installer installs MariaDB, PHP, Perl, etc. Hovering over the extension in FF task manager reveals a consistent rate of ~300-~500 dispatches per second, non-stop (again, even when the browser has no open tabs and has just launched) For VMs: Mac OS X 10.6 or later and intel (圆4) CPU not supported on M1 (arm64) CPUs. In firefox' task manager the extension is consistently the top energy user within the browser (always scores ~20 in the energy impact column - even when nothing is being downloaded and NO TABS ARE OPEN). One oddity is that the extension uses a lot of CPU cycles even when the browser first launches and has no open tabs !!! I love this extension and have used if for a couple of years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |