More control over CEF's own message loop

[yijiem]

I'm writing unit tests for our usage of CEF and my test is itself a CEF application. I want to test against our usage of cef message loop so in each test cases it does CefRunMessageLoop at the beginning and CefQuitMessageLoop at the end. But I found out CefQuitMessageLoop will not clear the tasks in the message loop and my later test case is affected by my previous test case. Any idea on how I can make it work? Is there a way to cancel remaining tasks in cef message loop?

Also it would be nice to have a CefQuitMessageLoopWhenIdle() which will return and quit the Cef message loop when all tasks have been ran. Thoughts?

[magreenblatt]

Are you posting the tasks that are still in the message loop, or are the tasks coming from CEF/Chromium internally?

If you are posting the tasks then you could make them cancelable. Alternately, you could post one final task that, via its execution, indicates completion of the previously posted tasks (because tasks are executed in order on the same thread).