Last year I wrote about AdBlock Plus’s effect on Firefox’s memory usage. The most important part was the following. First, there’s a constant overhead just from enabling ABP of something like 60–70 MiB. […] This appears to be mostly due to additional JavaScript memory usage, though there’s also some due to extra layout memory. Second, […]
Search: “adblock”
We found 15 results for your search.
[Update: Wladimir Palant has posted a response on the AdBlock Plus blog. Also, a Chrome developer using the handle “Klathmon” has posted numerous good comments in the Reddit discussion of this post, explaining why ad-blockers are inherently CPU- and memory-intensive, and why integrating ad-blocking into a browser wouldn’t necessarily help.] AdBlock Plus (ABP) is the […]
This is the first of the every-four-weeks MemShrink reports that I’m now doing. The 21 bugs fixed in the past four weeks include 11 leak fixes, which is great, but I won’t bother describing them individually. Especially when I have several other particularly impressive fixes to describe… Image Handling Back in March I described how […]
TL;DR Firefox 15 prevents most memory leaks caused by add-ons, including Firebug. For many users with add-ons installed this will significantly reduce Firefox’s memory consumption, without requiring upgrades to those add-ons. For those users, Firefox 15 is likely to be faster (sometimes drastically so) and less likely to crash, especially if they have multiple add-ons […]
Memory Reporting I changed things so that JavaScript memory consumption for web content is reported on a per-tab basis, as the following example shows. │ ├────4,472,568 B (00.50%) — top(http://www.mozilla.org/en-US/firefox/fx/, id=236)/active │ │ ├──4,192,640 B (00.47%) — window(http://www.mozilla.org/en-US/firefox/fx/) │ │ │ ├──1,979,112 B (00.22%) ++ js/compartment(http://www.mozilla.org/en-US/firefox/fx/) │ │ │ ├──1,607,216 B (00.18%) ++ layout │ […]
System Compartment Reporting With the recent landing of compartment-per-global, Firefox now regularly has 200+ system compartments at start-up. However, most of these compartments didn’t have names, which meant that they were merged into a single “[System Principal]” entry in about:memory and about:compartments. Until last week, that is, when Nils Maier added identifying information to the […]
There wasn’t much MemShrink activity this week in terms of bugs fixed, just bug 718100 and bug 720359. So I’m going to take the opportunity this week to talk about the bigger picture. Bug Counts As a prelude, here are this week’s bug counts. P1: 20 (-4/+0) P2: 131 (-3/+3) P3: 74 (-2/+7) Unprioritized: 4 […]
Add-ons This was the week of add-ons in MemShrink-land. Jared Wein fixed a problem in Firefox that was causing zombie compartments if you viewed a native video with any add-on installed that implements the nsIContentPolicy interface. Examples of such add-ons are Adblock Plus, GreaseMonkey, and NoScript, which are respectively the #1, #3 and #9 most […]
It’s been a quiet couple of weeks, due to Christmas, New Year, and all that. Two leaks in add-ons were fixed. cyberscorpio fixed a zombie compartment in the Super Start add-on. The problem was that the add-on was failing to remove an event observer when a page is unloaded. The fix will be present in […]
Adaptive Memory Behaviour The biggest news this week was that Justin Lebar landed code to make Firefox’s memory consumption adaptive on Windows. The code works by wrapping VirtualAlloc() and some similar OS-level allocation functions. Each time memory is allocated, the amount of available virtual and physical memory is measured by the wrapper. If either of […]