prehistoric-systems/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2026-03-11 09:04:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated Memory footprint: what happens inside µBlock after installation (markdown)

gorhill 2014-12-20 21:41:55 -08:00
parent 38266b11a9
commit 25c49a673f
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
Memory-footprint:-what-happens-inside-µBlock-after-installation.md

@ -1,11 +1,11 @@
1. µBlock will load the default selection of filter lists:
- This causes short-term memory churning (loading/parsing/sorting/storing), which short-term memory will be garbage-collected eventually
- All this short term memory churning causes µBlock's baseline memory footprint to grow further
1. After five minutes, µBlock will look whether one or more filter list need to be updated
1. After **five minutes**, µBlock will look whether one or more filter list need to be updated
1. If an update is needed, µBlock will flush from memory all filters and reload with the latest version
- This will causes another round of short-term memory churning, which short-term memory will be garbage-collected eventually
- Again, all this short term memory churning causes µBlock's baseline memory footprint to grow further
1. After seven minutes, assuming no change in selection of filter lists, or change in the content of selected filter lists, µBlock will snap a selfie
1. After **seven minutes**, assuming no change in selection of filter lists, or change in the content of selected filter lists, µBlock will snap a selfie
- Generating the selfie also causes short-term memory churning, which short-term memory will be garbage-collected eventually
- Again, this short term memory churning causes µBlock'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 µBlock's selfie