The root directory for installation-specific data and the parent directory
for profile-specific data. All CefSettings.cache_path and
CefRequestContextSettings.cache_path values must have this parent
directory in common. If this value is empty and CefSettings.cache_path is
non-empty then it will default to the CefSettings.cache_path value. Any
non-empty value must be an absolute path. If both values are empty then
the default platform-specific directory will be used
("~/.config/cef_user_data" directory on Linux, "~/Library/Application
Support/CEF/User Data" directory on MacOS, "AppData\Local\CEF\User Data"
directory under the user profile directory on Windows). Use of the default
directory is not recommended in production applications (see below).
Multiple application instances writing to the same root_cache_path
directory could result in data corruption. A process singleton lock based
on the root_cache_path value is therefore used to protect against this.
This singleton behavior applies to all CEF-based applications using
version 120 or newer. You should customize root_cache_path for your
application and implement CefBrowserProcessHandler::
OnAlreadyRunningAppRelaunch, which will then be called on any app relaunch
with the same root_cache_path value.
Failure to set the root_cache_path value correctly may result in startup
crashes or other unexpected behaviors (for example, the sandbox blocking
read/write access to certain files).
The root directory for installation-specific data and the parent directory for profile-specific data. All CefSettings.cache_path and CefRequestContextSettings.cache_path values must have this parent directory in common. If this value is empty and CefSettings.cache_path is non-empty then it will default to the CefSettings.cache_path value. Any non-empty value must be an absolute path. If both values are empty then the default platform-specific directory will be used ("~/.config/cef_user_data" directory on Linux, "~/Library/Application Support/CEF/User Data" directory on MacOS, "AppData\Local\CEF\User Data" directory under the user profile directory on Windows). Use of the default directory is not recommended in production applications (see below).
Multiple application instances writing to the same root_cache_path directory could result in data corruption. A process singleton lock based on the root_cache_path value is therefore used to protect against this. This singleton behavior applies to all CEF-based applications using version 120 or newer. You should customize root_cache_path for your application and implement CefBrowserProcessHandler:: OnAlreadyRunningAppRelaunch, which will then be called on any app relaunch with the same root_cache_path value.
Failure to set the root_cache_path value correctly may result in startup crashes or other unexpected behaviors (for example, the sandbox blocking read/write access to certain files).