Chromedriver and CefV8Context

[TomDigitale]

Hello,

We currently use chromedriver to test our application which use multiple CefClient. We encounter a problem when trying to use contexts in order to execute javascript:
without using chromedriver, everything works fine, contexts included.
But with chromedriver, during javascript execution (CefV8Handler::Execute()) every context is null.

For example, from the wiki:

Code: Select all

bool MyV8Handler::Execute(const CefString& name,
                          CefRefPtr<CefV8Value> object,
                          const CefV8ValueList& arguments,
                          CefRefPtr<CefV8Value>& retval,
                          CefString& exception) {
  if (name == "register") {
    if (arguments.size() == 1 && arguments[0]->IsFunction()) {
      callback_func_ = arguments[0];
      callback_context_ = CefV8Context::GetCurrentContext(); // <== callback_context_ is NULL
      return true;
    }
  }
  return false;
}

We are running on Linux 64, Ubuntu 14.04 and CEF 2171

Is this a known problem or is it related only to Chromedriver ?

Thanks.

[magreenblatt]

How are you executing the JavaScript?

[TomDigitale]

We are executing javascript in a mere index.html file with some javascript.
The function we are calling is implemented in c++ and using a callback function in one of its parameters.
Our implementation of CefV8Handler is similar to the one from the wiki (storing callback function and current context for a later use).

Like I said, the problem only occurs when using chromedriver to automatize tests for our application:
either CefV8Context::GetCurrentContext() or CefV8Context::GetEnteredContext return null once the chromedriver is plugged.

[magreenblatt]

We are executing javascript in a mere index.html file with some javascript.
The function we are calling is implemented in c++ and using a callback function in one of its parameters.
Our implementation of CefV8Handler is similar to the one from the wiki (storing callback function and current context for a later use).

Like I said, the problem only occurs when using chromedriver to automatize tests for our application:
either CefV8Context::GetCurrentContext() or CefV8Context::GetEnteredContext return null once the chromedriver is plugged.

This is the first I've heard of the problem but it sounds like a bug. Please add an issue to the CEF issue tracker.

[TomDigitale]

We opened an issue about this, and submitted a patch with minimal code to apply to cefsimple to highlight this issue.
We noticed that contrary to what we previously said, context is not null when executing CefV8Handler::Execute() for storing current context and callback function, but is null when using it after inter-processes communications, resulting in a crash when using Chromedriver while using callback functions.

Issue is here:
https://code.google.com/p/chromiumembed ... &start=200