Blow_Pop said:
despite having adblock enabled on it, it's failing to block stupid ads.
Since AdBlock works on a blacklist basis, it's only as good as the list you have. You can also add rules yourself, for anything you think is lacking.
TheArcaneThinker said:
Smooth Operator said:
Sadly FF got bloated over the years so it's not the best choice performance wise
Its not bloated . Just remove the toolbars and menus you don't need . I right now have nothing more than the menu bar and some tabs BTW you can press F11 to give your browser a better view .
1. F11 is a standard key for maximising most software. Well, anything that supports it, really - all other browsers for sure, as well as PDF viewers and so on.
2. Firefox
is a performance hog. It has historically had issues with memory usage and even with improvements seems to still be under-performing in that department. Memory leaks have plauged it to this day and seems that the garbage collection is something that can be improved on a lot. It's easy to test, even - if you have it open and you've used it for sufficient time for it to use a lot of memory (good number seems to be, say, 800 or more), going to about:memory and running cleanup doesn't free up as much memory as it could. Observing what happens there, it seems that sometimes FF holds on to some data for a given domain, as long as you have at least one tab open, even if the data is not relevant for that tab. I've seen it sometimes hold on to some data even after a tab has been closed, too.
In fact, I just found a neat trick - if you go to about:memory and just keep repeatedly hitting "Measure", the tab never lets go of the memory. Well, until you stop, that is, but you can rack up 400 meg in just several clicks. And a system monitor would show you a memory and CPU usage spike. This certainly seems to agree with my occasional observations - most of the domains I've seen rack up a lot of allocated memory also tend to be chatty making liberal use of AJAX calls, so perhaps the constant traffic to the page prevents GC from running on its space. It's not exclusively the reason, though - sometimes merely a heartbeat seems to keep the memory there. And I've definitely seen it sometimes not even cleaning up properly even after the tab was closed. Heck, it's even easy to replicate - 1. wait for FF to build up a lot of RAM usage 2. close all tabs but one 3. see how memory does not drop to the levels it was when FF was first opened.
OK, all the testing I've done is with some addons and customisation on, but nothing leads me to believe a vanilla FF is going to be faultless. Perhaps it would take longer to build up memory but the issues are present, as evidenced by the fact that FF has always been notorious for its resource usage.