Data leak/High CPU

[kryptoxide]

Web Example: Webmd

The issue is the the adblockplus extension is unable to block links as a function, but blocks the ad using the objects which are loaded within the site.

Currently there is an issue where AdBlock+ functions as intended, it blocks the ads on this site, although it does it hundreds of times.

The script on the site reloads the ad, and it blocks it again. I studied the internals of the site, just in case they had loaded a miner onto their site which was activated bu adblock or something, there are no scripts other than ads which function past the initial loadup which took about 7500ms in chrome.

225 requests, 2.4MB, 5.81s total loading time on the main site, okay cool.

Then you click on a article, watching the network usage in developer options, its loading scripts, gifs, and the XHR's which are blocked by ad block. 22,14 total seconds. Then if you take a look at the processes, the website is using upwards of 1.6GB of RAM, and consistently bouncing between a reload ~15% cpu usage, to upwards of 100% spikes and hanging there.

I'm unsure of how many sites are effected by this currently, but it needs to be looked into, for some reason, depending on the link you maneuver to within the site, the CPU usage can be debilitating to functionality of the site.

[mapx]

It's about one of the nastiest advertising system: instart logic.

The fix for this system (whic means a lot of sites using instart logic) is installing ublock origin extra (created by the same ublock origin creator - gorhill - Raymond Hill)
https://chrome.google.com/webstore/deta ... plco?hl=en

The extension is running fine together ABP or you can switch completely to uBo (ublock origin) - a very strong adblocker (ABP only now is implementing all the uBo features - after many years)

about instart logic (from the extension page ublock origin extra)

### Purpose

Instart Logic's technology used to disguise third-party network requests as first-party network requests, INCLUDING the writing/reading of third-party cookies. I consider this to be extremely hostile to users, even those NOT using a content blocker, as it allows third-party servers to read/write cookies even if a user chose to block 3rd-party cookies.

The company behind the technology understand how hostile its technology is to users, and thus tries to hide what is being done by making it difficult to investigate by detecting whether the browser's developer console is opened, and when it detects it is opened, it ceases completely to make use of the obfuscation mechanism. The developer console-detecting code works only for Chromium-based browsers however, and therefore the obfuscation technology is not used when using Firefox (a different web page is served for Firefox).

[mapx]

only for webmd you could also try (without installing ublock origin extra) adding as custom filter (see if works for you)

Code: Select all

webmd.com#$#abort-on-property-read btoa