Here are some insights and suggestions regarding your queries:
1. Disabling single_process_lock
Unfortunately, there isn't a direct flag or startup argument available in OBS to disable the single_process_lock feature. This change is part of the Chromium Embedded Framework (CEF) integration, which aims to improve stability but may limit certain use cases like yours.
2. Dynamic "root_cache_path" Setting
Currently, there is no built-in way to dynamically set the root_cache_path in OBS. The path is typically defined in the configuration files. You might consider modifying the OBS configuration files directly, but this approach may not be ideal for dynamic changes.
3. CEF Build Options
Regarding the possibility of the OBS team building CEF with --ENABLE_PROCESS_SINGLETON=0, this would require a change in the OBS source code and recompilation of the CEF library. You can raise this as a feature request or suggestion on the OBS GitHub repository, but it's ultimately up to the development team to consider such changes.
4. Implementing CefBrowserProcessHandler
Implementing a custom CefBrowserProcessHandler would also require changes to the OBS source code. This handler could potentially allow for more control over browser processes. Similar to the previous point, suggesting this feature to the OBS development team could be beneficial.
Recommendations
Check for Updates: Keep an eye on OBS updates, as they may address this issue in future releases.
Community Forums: Engage with the OBS community forums or Discord. Other users may have found workarounds or solutions that could help.
Feature Requests: Consider submitting feature requests or discussing your needs with the OBS development team on their GitHub page.
