When using Brave Browser (latest updates, based on Chromium), whenever I try to use the Customize button to do a parametric customization, I get a full page error on the next screen with no Debug ID.
If I use MS Edge, it works fine. I’ve tried setting Brave to Shields Down, adding it to a safe list for ad block, enabling Pop-ups and Redirects, Javascript, Javascript optimization and security, Web app installations. I’ve even tried briefly enabling Insecure content. Basically, everything under site-level permissions was enabled, but no change.
Has anyone else encountered this and found a solution?
Just a suggestion: why not switch to Vivaldi? Admittedly, the browser isn’t that well known because it’s not particularly flashy and is geared more towards professionals, but it has the same features as Brave. The difference is that Vivaldi focuses on compatibility and is funded by donations.
Brave has deteriorated over the years as they only care about money, which they need to survive. They have introduced Brave Ads, the Brave Rewards ecosystem and additional pay services.
The parametic works perfectly with Vivaldi, even with every protection on.
Thanks for the idea – I’ll check it out. I actually found that the problem may actually be my ARM-based Surface Pro 11, rather than Brave. When I try to access the Customize screen on Brave on my regular Intel-based desktop it works fine. I’m guessing the plug-in used in customization isn’t compatible with ARM processors. Of course, why then, would it work on MS Edge on my Surface Pro? Strange.
But don’t be surprised - Vivaldi uses quite a lot of RAM too, though less than most other browsers. The secret lies in its intelligent memory management system. When you’re using the browser but not actively accessing it, it switches to memory-saving mode.
In short, it uses a lot of RAM when you’re looking at it and less when you’re not. It makes sense to use RAM when you’re actively using the browser, and free it up again when you minimise it to the taskbar.
I have ram, just chrome and I guess this one eat it up. Studio is a bit of a hog as well. It also leaks like a sieve if you leave it open in the background.
