Are you about to suggest we add something or alter something to Brave? Don’t just tell us what you want - a lot of people want a lot of things. Instead, state your requested feature and state your case for why it should be seriously considered. You’re much more likely to get feedback from the team this way.
Please delete the text above the line before posting
Please support, possibly upstream support, for closing browser & associated, installed PWAs after browser update.
Backstory, Justification
I recently had trouble after an upgrade, with extensions not opening as expected. I googled the error, ChromeMethodBFE: 15::LockFile::1 issues with extensions acquiring locks on their settings files, followed advice to restart the browser and observed the issue still existed. I played a bit with observing the process tree, then, which I quit to restart again, notice that brave did not fully exit with my call to [(hamburger menu)] > Exit.
Uncaught (in promise) Error: IO error: .../LOCK: No further details. (ChromeMethodBFE: 15::LockFile::1)
m.xkcd.com/:1 Error handling response: TypeError: Cannot read properties of undefined (reading 'options')
at chrome-extension://nepmkgohgoagfgcoegjaggacodcpdibj/content_script/main.js:258:26
m.xkcd.com/:1 Unchecked runtime.lastError: IO error: .../LOCK: No further details. (ChromeMethodBFE: 15::LockFile::1)
m.xkcd.com/:1 Error handling response: TypeError: Cannot read properties of undefined (reading 'keyBindings')
at chrome-extension://nffaoalbilbmmfgbnbgppjihopabppdk/inject.js:62:37
m.xkcd.com/:1 Unchecked runtime.lastError: IO error: .../LOCK: No further details. (ChromeMethodBFE: 15::LockFile::1)
Request
I have many PWAs installed and in use, from a chat app, to two email clients, notes app, and I wish there were a way in browser to close them all in one click, after an update (or when debugging an issue) instead of needed to run $ killall brave in my terminal.