![]() (All these measurements are on a 64-bit build.) There are 429 documents on that page, which is a total reduction of about 1,550 MiB, reducing memory usage for that page down to about 450 MiB, which is not that much more than when AdBlock Plus is absent. the Vim Color Scheme Test) memory usage dropped by 3.62 MiB per document. ![]() Mozilla developer Nicholas Nethercote shared some numbers in July when a Firefox Nightly build was released with the fixes:įor example, on the above-mentioned “extreme example” (a.k.a. This meant that the memory consumption could skyrocket (up to 2GB in one edge case) as more copies were created. In short, Adblock Plus was registering a single style sheet for its element-hiding feature, but Firefox was creating a new copy of it for each page being loaded. Data structures that share the results of cascading user agent style sheets are now a go, which allowed the second issue ( bug 988266) to be fixed as well. Mozilla developer Cameron McCormack recently fixed bug 77999, enabling sharing of CSS-related data. But one of the bugs that contributed to the problem was actually first reported on Bugzilla in April 2001 ( bug 77999). This particular memory issue was brought up in May 2014 by Mozilla and by Adblock Plus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |