Mozilla Fixed a 14-Year-Old Bug In Firefox, Now Adblock Plus Uses Less Memory
An anonymous reader writes: Mozilla launched Firefox 41 yesterday. Today, Adblock Plus confirmed the update "massively improves" the memory usage of its Firefox add-on. This particular memory issue was brought up in May 2014 by Mozilla and by Adblock Plus. But one of the bugs that contributed to the problem was actually first reported on Bugzilla in April 2001 (bug 77999).
When will they fix the bug that's slowly turning Firefox into a crappy clone of Chrome?
Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
They also refuse to honor JPG rotation, because it might break the internet, without bothering to check and see if properly following the standard would make things better or worse.
Here comes Slashdot's resident spammer to tell us why browser extensions are bad, but some bullshit software he wrote (which just rides the coattails of other people) is good.
Notice he never addresses how advertising companies spin up new servers day in and day out, but no operating system's implementation of /etc/hosts will support wildcards on a domain. Blocking foo.adserver.com is useless when they create bar.adserver.com and baz.adserver.com an hour from now. Instead, he will ad-hominem attack anyone mentioning this.
Notice he never addresses the fact that advertising companies have begun serving their ads directly from IP addresses, bypassing DNS altogether. Instead, he will ad-hominem attack anyone mentioning this.
Notice he never addresses the fact that browser extensions can recognize and block certain DOM elements no matter where they come from, whereas a hosts file is completely incapable of assisting in this manner. Instead, he will ad-hominem attack anyone mentioning this.
Well, way to go Firefox! Right on top of things! But I thought Firefox has been saying for years it has no memory issues? So is this a 14 year old issue that really isn't an issue that now has been fixed? Got it.
And then close Firefox, open it again, with this post as the only tab. 349,349 K. Opening up a second tab takes it to 357,096 K.
So when you start Firefox has a base footprint of about 340 K + 8K per tab. (Depending on the contents of the page of course.) If it could actually _stay_ like that and recover memory properly when i close tabs then i wouldn't complain. Instead however there was about 1.6 GB of crap stuck in memory before i closed the program completely.
This Space Intentionally Left Blank
Any idea why it took them so long?