From 0c934b6896ab2caf85e78665ee7b28bdec42ed7e Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Fri, 13 Feb 2015 13:15:41 -0500 Subject: [PATCH] =?UTF-8?q?Updated=20Memory=20footprint:=20what=20happens?= =?UTF-8?q?=20inside=20=C2=B5Block=20after=20installation=20(markdown)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...-footprint:-what-happens-inside-µBlock-after-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md index 6c33fb8..95f60ad 100644 --- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md +++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md @@ -6,7 +6,7 @@ 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, but it is optimal to let µBlock take care of this + - You can disable auto-update if you want, but it is optimal to let µBlock take care of this, i.e. manually forcing an update is sub-optimal 1. **A few 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