CEF Forum

Adding log messages is generally discouraged, unless they're temporary to help with your development. In that case you can use DLOG from include/base/cef_logging.h

First full test on windows 64, i get the error below... is it ringing some bell ? how could i solve this issue that i didn't spot before ?

AppHandler.stateHasChanged: NEW
AppHandler.stateHasChanged: INITIALIZING
AppHandler.stateHasChanged: INITIALIZED
BrowserFrame.onAfterCreated id=1
[0202/002544.719:ERROR:stack_trace_win.cc(141)] SymInitialize failed: 87
[0202/002544.719:FATAL:thread_restrictions.cc(76)] Check failed: !g_blocking_disallowed.Get().Get(). Function marked as blocking was called from a scope that disallows blocking! If this task is running inside the ThreadPool, it needs to have MayBlock() in its TaskTraits. Otherwise, consider making this blocking work asynchronous or, as a last resort, you may use ScopedAllowBlocking (see its documentation for best practices).
g_blocking_disallowed currently set to true by
Error initializing symbols (87). Dumping unresolved backtrace:
00007FFA0EC2ABB2
00007FFA0DD1C122
00007FFA0DD924FD
00007FFA10E33E53
00007FFA10E33DC9
00007FFA0FDBE1CB
00007FFA0FDBE12D

What is the symbolized call stack for the thread_restrictions.cc error? You can download symbols at the same version and build (Debug/Release) from here and extract next to the CEF library.

Being in debug release,I took this one ...http://opensource.spotify.com/cefbuilds ... ls.tar.bz2 which contains libcef.dll.pdb (put aside libcef.dll)
but it seems not be taken into acccount, i've still unresolved symbols

it's perhaps related to this stackoverflow topic
https://stackoverflow.com/questions/125 ... 0/12865322, isn't it ?

I'll switch to release mode... and i'll let you know

Grrrr ...it seems that we have an Heisenbug ... this issue only occurs in Debug releases :-/

Ok for me ... this PR does exactly what i want (in Release mode).. Thank you for your help