@mk7z it’s possible, but it really matters on what the cause might be. If it was just something like a corrupt file or something, then reinstalling or just installing on top might fix whatever was broken and improve on things.
Not sure if you tried things like doing a different profile to see if it works any better.
Btw, is this still on your older Mac? If so, could always be that your browser also still is going to fetch components updates but Shields and all won’t have capabilities for it since not updating. I wouldn’t think it would cause many issues, but it’s possible. Not sure if you’d notice any impact with Shields off.
I did try using a different profile but found no difference.
I think I have stumbled across the source of the problems I’ve described and I’m sorry to say it really looks like something in Brave is the cause.
Why do I think that? . . . When this first started happening and I switched back and forth between Brave and Safari some of the same issues occurred in Safari but not to the same degree.
Because of all the problems I was having with Brave I had to switch to using Chrome. I had to get things done and Chrome is more like Brave than Safari is. However, at times I was running both Chrome and Safari and had no problem whatsoever with either.
Then I started testing using Brave with both Safari and Chrome (individually) and found that I had the familiar issues – but only when Brave was also in use. I’ve continued to do this testing and keep finding the same result. When Brave is running, either alone or together with one of the other browsers there are issues within Brave.
In a word, when Brave is run together with either of the other browsers the issues that occur in Brave seem to affect the other browsers. When Brave is out of the picture – no issues.
Meanwhile, sometimes Brave seems to run perfectly and I think it somehow cured itself (self-healing). That happened yesterday. Brave ran with none of the issues occurring for about two hours and then they started up again.
I don’t know how this could be fixed and I don’t think Brave team is going to be eager to look into my issues (not that I blame them), so it looks like I’m stuck using Chrome instead of Brave until I’m on an other computer (which I’ll probably have fairly soon).
BTW, throughout all the testing I checked memory and CPU levels and never saw any sign of stress or strain, so I don’t think any kind of resource overload was involved.
I do hate having to go to Chrome. But right now for me it works and Brave doesn’t.