From adc0480e16c5aace511416c6127fde8401a8b8a4 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Tue, 12 Aug 2014 22:03:29 -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 105f929..183bf48 100644 --- a/Myth:-µBlock-consumes-over-80MB.md +++ b/Myth:-µBlock-consumes-over-80MB.md @@ -11,6 +11,6 @@ If the browser is idle enough, before one minute has elapsed, the browser should ![µBlock's memory footprint](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/mem-footprint-at-launch-time.png) -The top image shows the memory footprint of µBlock right after launch. The image at the bottom shows the memory footprint of µBlock before one minute has elapsed while the browser is idle. +The top image shows the memory footprint of µBlock right after launch (Chrome 64-bit). The image at the bottom shows the memory footprint of µBlock before one minute has elapsed while the browser is idle. Note that once µBlock's baseline memory footprint won't change that much afterward. It will likely settles a few MB above the memory footprint reached after garbage collection has occurred, whenever the garbage collector is permitted to do its job. \ No newline at end of file