I have two instances of Chrome Capture running in Windows. Both have recently failed due to the chrome-capture-for-channels\chromedata\BrowserMetrics folder filling up with BrowserMetrics-xxxxxxxx-xxxx.pma files. Like hundreds of gigs worth. This appears to be specific to the Chrome Capture installation, and not the Chrome browser configuration. Chrome has a setting under privacy and security that controls metrics reporting. I think that controls the creation and transmission of those files. The setting has no effect on cc4c, though. Maybe there is an embedded launch flag that overrides it? Any ideas about how to prevent this behavior?
After cleaning up the files on both systems, main.js fails every time with the error message:
[2025/08/08 10:55:57.352] GET /stream/msnbc from ::ffff:192.168.3.150 responded 500 in 719.849 ms
[2025/08/08 11:00:35.284] failed to start browser page Watch the MSNBC Live Stream - NBC.com Error: Failed to launch the browser process!
Manually starting Chrome with the same url works fine. I'll spend some time with a debugger, so maybe I'll get a clue that way.
-Jay