Hello
We're currently testing CEF 120 in our application, on windows 10, and we have a crash in a rare situation :
+ two processes are launched
+ the processes's cef settings about cache (cache_path and root_cache_path) have an empty value (*).
+ Then the second process crashes. It emits the following recent warning :
WARNING:resource_util.cc(94)] Please customize CefSettings.root_cache_path for your application.
Use of the default value may lead to unintended process singleton behavior
(*) : we empty these two settings during test replays in order to avoid instability due to cache content.
To reproduce the issue on cefclient from CEF120, it's only necessary to activate the multi_threaded_message_loop :
1) For example, in MainContextImpl::PopulateSettings from file tests\cefclient\browser\main_context_impl.cc
add the following settings value at the end of the method and rebuild
settings->multi_threaded_message_loop = 1;
2) Launch first cefclient : it's ok.
3) Launch another cefclient without closing the previous one : crash with the following log content
[1219/143816.198:WARNING:resource_util.cc(94)] Please customize CefSettings.root_cache_path for your application. Use of the default value may lead to unintended process singleton behavior.
[1219/143816.234:FATAL:ref_counted.h(220)] Check failed: !in_dtor_.
and the call stack of the crash is in the UI THREAD, while in the main thread the method CefInitialize has previously failed.
With the same modifications (multi_threaded_message_loop) in CEF 118 and the same scenario, the crash did not occur and both cefclients are working fine.
Does someone know if the memory cache mode (i.e. when cache_path and root_cache_path are empty) is no more supported ?
maybe when combined with multi_threaded_message_loop?
Thanks