Memory "leak" when using the C API

[bclai]

Hi!

I am using the CEF's C API to implement my application. On cef_shutdown, there are unreleased objects.

From the code, it looks like CEF's Wrap function will increment the reference count. Since I am not doing anything on the C-side (application-side) yet, there reference count increases everytime the handler is called.

So my question is, am I supposed to release all CEF objects manually on the C-side (application-side)? Or is there a way to generate the inverse CEF C++ wrappers for use on the application-side.

I also encounter this issue, but in reverse, when I export an object to Javascript from the application. set_value_bykey will decrement the reference count, so I currently increment the reference count manually before calling set_value_bykey.

While I can use C++, I cannot use the CEF C++ API directly because my application links to the standard libraries as a DLL, while CEF/Chromium links to them as a static library. If I remember correctly, it causes link errors. This is why I am using the C API instead.

Thanks in advance.

Johnny

[magreenblatt]

Please read the Wiki post on C API reference counting: http://code.google.com/p/chromiumembedd ... ingTheCAPI

If you build the libcef_dll_wrapper project with the same runtime configuration as your application then you shouldn't have any linking problems when using the C++ API.