@289wk @Mattches Thanks for the replies, I believe I found what the issue is.
First of all, I tried all of the following, with no effect on the behavior:
- Creating a new profile, restarting Brave and selecting that new profile
- Using a private window (from the new profile)
- Clearing browsing data (cookies, history, cache, history, etc.) and restarting
However, I noticed that when running using the following command:
brave-browser -n --args --incognito --no-experiments --disable-extensions --disable-gpu
The issue seemed to be resolved.
I then tried completely reinstalling Brave, and deleting the folder ~/.config/BraveSoftware, and could not reproduce the issue after going through the initial setup.
I believe the issue is caused by the flag #ozone-platform-hint. I have been in the habit of immediately setting this flag to “Wayland” in chromium-based browsers due to the fact that it resolves some odd issues when running on Wayland (e.g. touchpad scrolling feels pretty bad without it, and there’s a ~1px line at the top of the window even when maximized which cannot be clicked on, so attempting to e.g. select a tab by clicking on that top pixel of the screen just selects the window behind Brave). I previously tested disabling it & setting it back to X11, but I had no luck. However, I believe it was actually not fully taking effect even after relaunching Brave after changing the flag. In my testing just now, in order to have the flag actually take effect, it seems like just relaunching is not sufficient, and I have to fully pkill the Brave processes and re-open the browser manually.
TL;DR I’m pretty sure the issue is caused by the #ozone-platform-hint flag. Unfortunately, there are some other issues that occur when #ozone-platform-hint is set to the default (X11), so I’m probably just going to use FIrefox until this is resolved and I can use Wayland as the preferred Ozone platform backend without the hitching/stuttering issues.