Skip to content
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.

0.8.8.0
Compare
Choose a tag to compare
@gorhill gorhill released this 15 Feb 21:13
· 888 commits to master since this release
0.8.8.0
532d2b3

Reminder: Chromium (or browsers based on) still suffer from that ugly bug which causes a big chunk of memory leak each time a user opens the popup UI of an extension. Therefore, the more you use the popup UI in Chromium, the larger the memory footprint of µBlock (or any extension really) will grow. I've already seen feedback like "doesn't have a µ memory footprint at all for me. >250MB" (for µMatrix). This is important to keep this Chromium memory leak bug in mind if you make use of dynamic filtering, as this feature requires frequent access to the popup UI.

Changes & enhancements

Safari

Important (though minor) improvements in request capturing(gorhill/uBlock@d2cc20ed47)

  • Bonus: out-of-the-box support for HTML5 twitch.tv (some users may need to disable Flash to get the HTML5 player)
Core

All dynamic rules are temporary by default: Click the padlock if you want to persist the ruleset for a specific web site.

  • The padlock will be visible if and only if there is at least one temporary rule in the pane
  • This is really the optimal way to use dynamic filtering, as using this feature is often a matter of trial and error
  • This prevents ruleset pollution: your ruleset will be only those which you will have explicitly persisted
  • If you Ctrl-click to set/unset a rule, it will be immediately persisted (command ⌘-click on Mac)

µBlock's power button's color is now 450nm-blue-LED: green could lead to confusion given that in the dynamic filtering pane, green is used to denote that network requests won't be blocked.

The assets auto-updater has been rewritten, to work in a more gentle and discrete way

  • Assets which need to be updated will be fetch one by one in the background, with a good delay between each fetch (this prevents large peak in memory and network bandwidth usage)
  • Once all assets have been updated, they will then all be reloaded using their locally cached copies
  • The optimal way to update assets in µBlock is to let auto-update do the job: it is more gentle on resources locally and also more gentle to remote servers

Closed as fixed

Firefox
Safari
Core
Assets 4