![]() I have a slew of bash functions according to what I want to see come up, (Of course I get all the previously opened tabs.) > without using extensions or addons from outside the debian repositories?Īfter installing it, I type, say, my-cups to open up the browser forĬUPS administration. > I would sure be interested in your method of running firefox on stretch, Of weeks or so, and then there were all those scripts that "stopped The latter would crash about every couple Plugin-container processes are pretty rare, presumably being replacedīut my experience is that FF on stretch is a lot more reliable than I have noticed that the old xul…runner processes have gone, and that > service will likely be resumed in buster. > I think that ESR 60 with unpackaged extensions is the lesser evil. > Debian is wedged between upstream dropping support for xul-ext-* extensions in ![]() > xul-ext-* packages before webext-* packages are available. > I agree that it is sad that Firefox on stretch has been upgraded to break the > workaround is to install them directly from upstream via Firefox. I did not see any webext-* packages in stretch-backports. > suggests that webext-* packages are coming to stable. > My point is not that you should use unstable, but that the evidence on sid The paid-for links at the top of google searches. Sites that notice you're blocking ads, and the inability to click on Using it because the side effects are so minor: occasional nagging by ![]() I originally did this because the adverts would totally overload aīrowser running on a 1.5GHz laptop with 500MB memory. (The rest of the file is static addresses for my LAN.) I find a lot of adverts are blocked by my very long /etc/hosts file. > thanks anyway but I think your advice is a little dubious. and I use stable, because it is stable, not sid, which is unstable. > I see that there is a webext-ublock-origin for sid but I have never used > the xul-ext-* extensions are now broken? > How exactly do you think stretch users should run an adblocker when all Good ad blocker like uBlock Origin will help a lot. Now take up 90% of most web processing time and space. I don't know what that is, exactly, but advertising and trackers Web pages demand be run: JavaScript, CSS animations, weird media The Web Content process(es) are fired off to run things that the Web pages, decoding them, and some of the rendering work. The main Firefox process handles the user interface, fetching That's because Firefox is now multiprocess. > they appears even if I disable all modules. > I think also these "web content" threads are the causes of my problem. > files are being written continuously to your hard drive. > I've seen something like this is when an app has crashed into an > hazard a guess as to what's causing the high CPU usage. > Also, check what those three "web contents" are. Firefox Quantum only shows on average 3 to 4% RAM > you have very little RAM to begin with. > First, Firefox is using 50% of your RAM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |