Hello! I also have this issue occurring and created a topic and the only solution, as per @Mattches’ last response in said topic was to simply wait for the Chromium team to address/fix this issue.
TL;DR — it’s an upstream Chromium issue and Brave cannot do anything until Chromium team fixes it.