How to quit the application safely?

[chenon]

I found that the cef application occasionally crashed when main window closed by user.
It raised error message about reference count.

To confirm this problem, I add a Sleep() in function ProcessRequest in scheme_test.cpp.

Code: Select all

virtual bool ProcessRequest(CefRefPtr<CefRequest> request,
                              std::wstring& mime_type, int* response_length)
{
  bool handled = false;

#if 1 //add delay here
  Sleep(5000);
  //PostMessage(AppGetMainHwnd(), WM_DESTROY, 0, 0);
#endif

  Lock();
  ...
}


If closing the main window in the 5 seconds on sleep, the cef will raise the error information and then crash.

I get the similar error when using message WM_DESTROY instead of Sleep().
Only seen the error message in debug mode, shown as the attachment. Is it a bug?

[magreenblatt]

This assert means that a reference to a CefHandler object is being kept past the call to CefShutdown(). This is not unexpected since, in your example, the protocol handler is still executing when the application window is closed. The notification is intended for informational/debugging purposes.

[chenon]

Thank you! So it should be OK since that we use "Release" mode for real product.

CEF is the best framework for applications with WEB UI!

[magreenblatt]

So it should be OK since that we use "Release" mode for real product.

In this particular case you're fine (see http://code.google.com/p/chromiumembedd ... ail?id=113 for one potential caveat). Worst case hitting these asserts may mean your application isn't using the smart pointers correctly. For instance, if you make a change to your code and suddenly start hitting these asserts then you may have introduced a memory leak. However, since CefShutdown() is generally called when the application is exiting, potential memory leaks aren't necessarily an issue because in any case the OS will reclaim all memory when the application exits.

CEF is the best framework for applications with WEB UI!

Glad you like it .