Description of the issue:
Audio / Video capture is not blocked and a memory leak starts to grow if you visit a page and refresh it a few times. Audio/video capture is not being blocked.
Update from 1.95.101 to 10.95.104 is where the issue started again.
Open Brave without any tabs or anything in background loading.
Visit a site that invokes audio / video capture. (discord.com, x.com, etc.)
Press shift + esc to view browser task manager. Identify audio process and video capture running without a need for it.
Refresh the page a few times and verify memory usage continues to increase.
Even when AudioCaptureAllowed & VideoCaptureAllowed both set to false in brave:policy it will not stop it from loading. Video capture will sometimes follow the policy and others it will stay.
Steps to Reproduce (add as many as necessary): 1. 2. 3.
Open brave browser
Visit page that invokes video capture
Review browser task manager to identify processes and memory
Actual Result (gifs and screenshots are welcome!):
Memory leak on webpages that hold audio / video capture.
Expected result:
Audio and Video capture to be blocked and no memory leak.
Reproduces how often:
Everytime you visit a page that invokes audio/video capture.
Operating System and Brave Version(See the About Brave page in the main menu):
Brave official 1.95.104 Chromium: 153.0.8010.53 (Official Build) (64-bit)
Brave://flags are all the variations being set every single time they update the browser. They even set variations with each new build which are viewable under brave://version.
You are referencing the brave generic group policy settings which only mentions a few brave specific group policies and not everything that alters the browser. Brave inherits some (not all) group policies from chrome and would have to reference https://chromeenterprise.google/policies/ along with brave coding to verify what does and does not work.
This wasn’t a issue till they changed to latest chromium version. This has occurred before.
For more specific observation of memory being used:
Because Memory Footprint alone, doesn’t yet tell us whether that memory is associated with the webpage, the renderer, the media machinery, or something surviving the navigation.
