This is interesting.
Extension:Brave always was Brave Shields Button/Panel UI.
There was a way to disable it on start by using –disable-brave-extension to start Brave, the Shield’s icon would disappear and you would get no panel or Extension:Brave process for anything.
The thing about Brave’s adblocker is that it is native and always works as long as the settings say so, so even if there was no UI or Brave shields icon, the work of the adblocker never stopped, that’s why I always used that flag in the past, because Extension:Brave was a waste of resources since I never even opened Shields panel to see what was being blocked or controlled shields through it because it messes with the preferences file and I hated it.
But with the release of Shields v2 Panel update, seems like Extension:Brave shouldn’t even be a thing anymore, it should not even be there at all. Because when you use --disable-brave-extension the extension:brave process disappears but the Shields v2 icon/UI/panel is there and it works just fine.
I remember that being a thing like if I enabled ShieldsV2 flag in Nightly when it was being developed you would get to see two Shield icons on the address bar. And if you started Brave disabling the Brave Extension and then you would only see the new one, and the v1 would be disabled with the extension:brave process.
So, it seems like you (nobody) shouldn’t even be getting this, because shields v1 is not a thing anymore so the Extension:Brave shouldn’t have any presence anymore in Brave Browser. It is a waste of memory and maybe an extension caused the issue or a page or whatever but I really don’t see why extension:brave process is still there wasting resources, for example, when I launched Brave without disabling that extension:brave used 23,000K for normal windows and 18,000K for inPrivate windows, so that was 41,000K memory wasted unnecessarily and since Shields v1 is not a thing anymore, why is it still there?
Chromium extensions work like if an extension is allowed in inPrivate mode then it will be spawned twice, and if you open a new profile in Brave, Shields will be loaded one more time, so if I opened 10 profiles, there would be 230,000K of useless and wasted memory because of extension:brave which again, shouldn’t be present anymore because Shields v1 is not even a thing anymore, it can’t even be enabled by flags like in the past.
So test Brave with --disable-brave-extension and see how it goes, I mean, you are disabling it so I don’t think you will have a problem anymore.