Updated Myth: µBlock consumes over 80MB (markdown)

Raymond Hill 2014-08-12 22:07:24 -07:00
parent adc0480e16
commit df7f530aee

@ -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 (Chrome 64-bit). 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) (Expect similar memory footprint each time the filter lists have to be reloaded). 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.