@Vortex123211,
Hmm let me reach out to some additional team members. You may have been right originally about it being a system setting, but if that was the case we would expect similar behavior in chrome/chromium. Since that’s not the case there must be something else at play.
@Vortex123211 i read on other post but i forget that the other guy has nvidia vga and he change one of the setting in the nvidia setting
it was not same as your issue but not sure if there setting in your video card could solve it
I’m sorry for the long wait @Vortex123211. I do not have a solution yet unfortunately – I’ve just now bumped/pinged several team members to see if anyone is free to get eyes on the issue. Hope to have more information soon – again, appreciate your patience.
@Mattches@justsomeone1 . Its been a few days. The problem is still persisting. I even Factory reset windows and reinstalled brave. But the same problem still is there. Would appreciate a solution on the same ASAP.
@Vortex123211,
I’m really not sure what is causing this issue for you. My inclination is to think it’s an OS issue but again, that doesn’t make sense if other browsers don’t show the same behavior.
When you reinstalled Brave, did you also wipe the associated browsing data or did you just uninstall the application and then reinstall it? It might be worth a full reinstall if possible. Also, have you updated to the latest build (v1.25.68 at the time of writing this)?
Yes @Mattches . I am running the latest version of the browser right now and i noticed a temporary fix. If i turn on Hardware acceleration this problem doesn’t occur as far as i have used till now. IDK why but i just randomly tried it out after going through some similar complaints. Pls see if this helps you figure out my issue. The only downside is that this consumes a crazy amount of memory. I tried it an my laptop started crashing immedietely.
UPDATE… Turns out, I had Chrome and Edge with Hardware acceleration turned on by default. Once i turn that off, then even they show the same problem. Sorry for the error earlier. I think this is the issue. is there any fix? @Mattches Any solution?