Description of the issue: Tradingview.com performance degrades over time and constantly has to be reloaded to get a brief moment of performance it’s gotten so bad I now have to have another browser open to be able to have tradingview up. Neither Chrome or FF has similar problems.
How can this issue be reproduced?
1.) Open tradingview.com , with a watchlist with 60 symbols and 5 indicators and wait for a bit, usually have ot in the background or on a virtual desktop switching to every now and then.
2.) Try switching between symbols in the watchlist and see how it lags and barley can do it without reloading tradingview
Expected result:
slow performance panning around and unable to switch symbols.
Brave Version( check About Brave):
version v1.71.121
Troubleshooting technical issues is much easier when both the user and support agent practice clear communication. For this reason, we have provided the template below for you to fill out with information about your issue. Please provide as much detail as possible so we can most efficiently resolve your problem.
Delete the any text above the line separator below before posting
Does the site function as expected when Shields are turned off?
Is there a specific Shields configuration that causes the site to break? If so, tell us that configuration. (yes/no):
Does the site work as expected when using Chrome?
Brave version (check About Brave):
ADDITIONS TO THE CURRENT TEMPLATE:
Operating System & Version:
Have you tried testing things in a NEW Profile? (Brave Settings > More Tools > New Profile or Guest Profile)
(Yes/No?):
AND/OR
Have you tried testing things in a different version of Brave? (e.g. Beta, Nightly)
(Yes/No?):
Do you have any Extensions enabled? (yes/no, if yes, have you tried disabling them one-by-one to test?):
Do you have any other Privacy/Security applications OUTSIDE of Brave? (VPN, Adblockers, Anti-Virus/Malware, Firewalls, etc.) (yes/no, if yes, have you tried disabling them one-by-one to test?):
SIDE NOTE for other support: @Mattches & @Saoiray (do you think it might be worth updating the templates with the above information? or a modification maybe to some of it )
In the end after some investigation it seems to have been a extensions fault, which is ironic because it was the exact extension i replaced because the previous one doing the same thing was degrading performance.