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:59:54 -08:00
parent a4f49d3e85
commit e4690c0411
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

@ -6,6 +6,7 @@
- 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 make a selfie
- A selfie allows µBlock to skip the parsing/sorting of data, a typically CPU and memory intensive operation
- 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