The issue described at Major CPU Spikes on RBC Canada Online Banking is still happening. Brave spins off 16-18 dedicated worker threads, and pins the CPU for ~50 seconds before the page becomes responsive. It is still an issue with shields down and in a private window.
Expected result:
Page should be responsive in a reasonable time frame.
Brave Version( check About Brave):
Version 1.40.109 Chromium: 103.0.5060.66 (Official Build) (64-bit)
Additional Information:
According to the previous post linked, this is an issue with blocking fingerprint/port scanning scripts, but shouldn’t those scripts be allowed with shields down, or shouldn’t there be a way to add exclusions to allow those scripts?
I’ve reported this issue to TD, but their response is that it’s a browser issue and that they’ll add notes to the case file, which in call center lingo means but nobody will ever look at it.
After some more testing, td.com seems to work just fine with shields up, and only misbehaves when shields are down. That’s fascinating.
Turning shields back on fixes the problem, but it may indicate something else not being handled properly when shields are down. Maybe the list is only being checked when shields are up? Something akin to:
if (ShieldsUp)
// Checks list, allows td.com scripts
else
// Doesn’t check list, and blocks scripts by default
I would call this specific issue resolved, and leave it to you if a deeper dive into the code is warranted.