diff options
| author | Raymond Hill <gorhill@users.noreply.github.com> | 2015-07-03 12:39:51 -0400 |
|---|---|---|
| committer | Raymond Hill <gorhill@users.noreply.github.com> | 2015-07-03 12:39:51 -0400 |
| commit | 7161c21b14ffb1e6ccedc90d28b6f78b6cf6335c (patch) | |
| tree | 22823de7b02a24909df10ecf814be54811054d49 /README.md | |
| parent | 352ef808f1cd0af1e745a18d261fff5d5d4913b3 (diff) | |
| download | uBlock-7161c21b14ffb1e6ccedc90d28b6f78b6cf6335c.zip uBlock-7161c21b14ffb1e6ccedc90d28b6f78b6cf6335c.tar.gz uBlock-7161c21b14ffb1e6ccedc90d28b6f78b6cf6335c.tar.bz2 | |
Update README.md
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -98,7 +98,7 @@ Firefox<br> <sup>[1] Details of the benchmark available at <a href="https://github.com/gorhill/uBlock/wiki/Firefox-version:-benchmarking-memory-footprint">Firefox version: benchmarking memory footprint</a>.</sup><br> -<sup>[2] Important note: There is currently a [bug in Chromium 39+ which causes a new memory leak each time the popup UI of an extension is opened](https://code.google.com/p/chromium/issues/detail?id=441500). This affects <i>all</i> extensions. Keep this in mind when measuring Chromium's memory usage. In the benchmarks, I avoided opening the popups completely.</sup><br> +<sup>[2] Important note: There is currently a [bug in Chromium v39 to v41 which causes a new memory leak each time the popup UI of an extension is opened](https://code.google.com/p/chromium/issues/detail?id=441500). This affects <i>all</i> extensions. Keep this in mind when measuring Chromium's memory usage. In the benchmarks, I avoided opening the popups completely.</sup><br> #### CPU |