From 7fc73c190545b19515a3063c2c7eed66e8d2f927 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Tue, 12 Aug 2014 21:58:32 -0700 Subject: [PATCH] =?UTF-8?q?Updated=20Myth:=20=C2=B5Block=20consumes=20over?= =?UTF-8?q?=2080MB=20(markdown)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- Myth:-µBlock-consumes-over-80MB.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Myth:-µBlock-consumes-over-80MB.md b/Myth:-µBlock-consumes-over-80MB.md index a35b4cb..335bda0 100644 --- a/Myth:-µBlock-consumes-over-80MB.md +++ b/Myth:-µBlock-consumes-over-80MB.md @@ -1,7 +1,7 @@ I've seen a couple of instances of people claiming µBlock is not as memory efficient as claimed. Examples: - ["I just installed it, and it uses 117MB - that's not even close"](http://www.reddit.com/r/chrome/comments/2cpogs/fast_and_light_ad_blocker_for_chrome_%C2%B5block/cjhutwz) -- ["Simply tried, did not see where the province of memory" (lol translation)](http://bbs.kafan.cn/thread-1762885-1-1.html#pid32323303) +- ["Simply tried, did not see where the province of memory" (Google translate...)](http://bbs.kafan.cn/thread-1762885-1-1.html#pid32323303) When µBlock launches, it loads each filter file, parse the content, eliminate duplicates, than instantiates the filters using optimal representation. This parsing of the filter lists requires a good amount of temporary memory.