From fed089ea4b75bee8583f49735e521055a7987c34 Mon Sep 17 00:00:00 2001 From: gorhill Date: Sat, 20 Dec 2014 22:01:44 -0800 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 a67b7b7..133e730 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 @@ - 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 + - 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 - Any change in the selection of filter lists, or change in the content of selected filter lists will invalidate µBlock's selfie