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)

Raymond Hill 2015-02-13 13:13:51 -05:00
parent 56a1dd82bf
commit 83153315c9
1 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -1,12 +1,13 @@
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. **Five minutes later**, µBlock will look whether one or more filter lists need to be updated
1. If an update is needed, µBlock will flush from memory all filters and reload with the latest version
- All this short-term memory churning causes µBlock's baseline memory footprint to grow further
1. **A few minutes later**, µBlock will look whether one or more filter lists need to be updated
1. If one or more filter lists need to be updated, µBlock will launch a background task which will fetch an updated version of whatever filter list is deemed obsolete
1. Once all filter lists are brought up to date, µ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
- You can disable auto-update if you want, but it is optimal to let µBlock take care of this
1. **A few mintues 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
- Again, this short term memory churning causes µBlock's baseline memory footprint to grow further