Skip to content
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.

Memory footprint: what happens inside uBlock after installation

Jump to bottom
Gitoffthelawn edited this page Jun 8, 2015 · 9 revisions
  1. uBlock will load the default selection of filter lists:
    • This causes short-term memory churning (loading/parsing/sorting/storing); short-term memory will be garbage-collected eventually
    • All this short-term memory churning causes uBlock's baseline memory footprint to grow further
  2. A few minutes later, uBlock will look whether one or more filter lists needs to be updated
  3. If one or more filter lists need to be updated, uBlock will launch a background task which will fetch an updated version of whatever filter list is obsolete
  4. Once all filter lists are brought up to date, uBlock will flush from memory all filters and reload them with the latest version
    • This will cause another round of short-term memory churning; short-term memory will be garbage-collected eventually
    • Again, all this short-term memory churning causes uBlock's baseline memory footprint to grow further
    • You can disable auto-update if you want, but it is optimal to let uBlock take care of this, i.e. manually forcing an update is sub-optimal
  5. A few minutes later, assuming no change in selection of filter lists, or change in the content of selected filter lists, uBlock will make a selfie
    • A selfie allows uBlock to skip the parsing/sorting of data next time it loads
    • Generating the selfie also causes short-term memory churning; short-term memory will be garbage-collected eventually
    • Again, this short-term memory churning causes uBlock's baseline memory footprint to grow further
    • Any change in the selection of filter lists, or change in the content of selected filter lists will invalidate uBlock's selfie
  6. Even after the growth in memory baseline, uBlock's own memory footprint is still quite a bit smaller than that of Adblock Plus (ABP) -- once the garbage collector does its job
  7. uBlock's contributed memory footprint to web pages is much smaller than that of ABP
    • The contributed footprint to web pages is part of the memory footprint of the web pages themselves
    • As opposed to an extension's own memory footprint, visible using Chromium's "Task Manager", the contributed memory footprint to web pages cannot be easily seen by users
    • Though this measure is not readily visible, it is where you get the biggest bang for the buck with uBlock compared to ABP -- because uBlock does not inject thousands of CSS rules into pages and embedded frames (unlike ABP)

Once you have reached the point where there is a valid uBlock selfie, µBlock will run the most efficiently.

The next time you launch uBlock and there is a valid selfie, the load time will be a fraction of the load time when no selfie is available [1], and uBlock's baseline memory footprint will be smaller than when uBlock launches without a selfie available.

In summary, uBlock will perform at best efficiency if you give it time to optimize itself after installation. In subsequent launches, uBlock will perform more efficiently than what you may have observed immediately after you installed it.

[1] See https://www.youtube.com/watch?v=BpypOeK10N8

Also, if you want to look at memory figures, in addition to the above notes regarding garbage collection, keep in mind:

  • The Chromium bug which causes a memory leak when opening any extension's popup UI.
  • Currently opened extension option page(s) contribute to increase the extension's memory use
  • Sometimes a browser's garbage collector ("GC") is lazier than others, i.e. it may takes longer to kick in.
    • In benchmarks, sometimes a GC cycle had to be forced using dev tools.
Clone this wiki locally