Mirrors
/
uBlock
mirror of https://github.com/gorhill/uBlock.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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

Raymond Hill 2015-01-13 21:08:26 -05:00
parent 0239b37e10
commit b4db20bbae
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -5,6 +5,7 @@
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
- (You can disable auto-update if you want)
1. **Seven minutes later**, assuming no change in selection of filter lists, or change in the content of selected filter lists, µBlock will make a selfie
- A selfie allows µBlock to skip the parsing/sorting of data next time it loads
- Generating the selfie also causes short-term memory churning, which short-term memory will be garbage-collected eventually