Are you using it in a flatpak
Running Brave here no issues but its repo
When you say destroyed?

WetGeek I think you neet to run:
find ~/.cache -name GPUCache -exec rm -rv {} +
find ~/.config -name GPUCache -exec rm -rv {} +

It fixed my Heroic launcher, i think the mesa fix brought back the need to fix chromium based apps.

    WetGeek

    Hi,
    you are right with this Bug, Because i have it too on a absolutly normal laptop (Intel i5 onboard GPU) and the stable Vivaldi from the Solus repo!

      Same here on Solus Brave. Thanks for the fix!

      I never had Vivaldi installed on this machine
      Installed both flatpak and repo they both seem to be fine.
      (Just info)

      WetGeek I wonder if any other Chromium-based browsers were affected

      In my case, after today's update Brave has been behaving strangely, with some images not loading.

      ReillyBrogan If you have rendering issues with Chromium apps after the Mesa update please run the commands in our troubleshooting article.

      And this solved it. Thank you very much.

            WetGeek . I wonder if any other Chromium-based browsers were affected.

            my flatpak ungoogled chromium is fine--so a mesa/vivaldi exclusive perhaps.
            be curious if the troublshooting article will help you. I know Vivaldi is your daily browser. good luck WG.

            edit: brain fart; wrong browser cited for WG. THanks @elfprince !

                That little birdie was whispering in my ear telling me why?

                Why did I not have any issues with the recent gl update.
                Well I figured out why (Bleachbit) I have been running everytime I shut off computer because I was testing
                Software. and alot of times after I unistalled something (I know to much..lol)
                After looking through what bleachbit was going to delete it was filled with the mesa caches and even the brave
                ones and that was the (ah ha moment).
                I am sure this is alot how I got bleachbit set up but it was interesting so I posted.
                Note: guess I need pay more attention on what its doing.

                  Axios ed with the mesa caches and even the brave
                  ones and that was the (ah ha moment).

                  brave tends to get fat for some reason but this one always irritates me:

                  Do I need 7,700 mesa shader files?

                      brent Ya even thoo I got brave to delete on close
                      If I bring up bleachbit there is always about 50meg their.
                      so you are right it appears it does not clean those.
                      Firefox is always nill to nothing.
                      (I have always been big cleaning caches to keep the uglies out.)

                        Discord 0.0.38 cherry-picked.

                        Cache exists for a reason, we are only telling you to delete specific parts as a work around for a Chromium bug. Deleting it for no real reason just slows down the application that uses that cache as it will be generated fresh again when needed.

                          @ReillyBrogan, I have a question for you. For years I've known what "rolling" means when applied to Solus, as I've gone from one version to another just by routinely updating, starting with Solus 3.9999. What I''m not sure about, is whether this applies to pre-release versions as well.

                          i've created 4 VMs for testing Solus 4.5, and as RC1 is eventually replaced, and the replacement is eventually replaced, will those VMs eventually evolve into released versions of Solus 4.5, and identical to ones that have been created with the final 4.5 .ISOs?

                          I'm trying to find out whether I'll need to download new .ISOs as they're released, and create new VMs based on those .ISOs each time. It will mean so much less work if I can simply keep these devices fully updated.

                            WetGeek Well, the RC1 ISOs went out with a bug where they are pointed at the unstable Solus repo so at minimum you'd want to switch them to the stable repo. Other than that, maybe? We're not limiting ourselves to changes that mean that updating an RC1-installed system would have an identical result to installing from final 4.5, though I do not believe that we've made any such changes yet.

                                ReillyBrogan at minimum you'd want to switch them to the stable repo

                                Should I take it from your comment that I should do that when 4.5 is publicly released, or would it be okay to point all these VMs at Shannon starting now? I just don't want to do something now that I later find out was unwise.