Is this a memory leak?

[Dimitris Kounalakis]

  if not (csDesigning in ComponentState) then
    FHandler := TVCLClientHandler.Create(Self);

This is returned as a memory leak.

[Dimitris Kounalakis]

I put the following to the formclose event and it is fixed.

if CefSingleProcess then begin wachromium.Load('about:blank'); // avoid AV when closing application
while wachromium.Browser.IsLoading  do Application.ProcessMessages; end;

[Architector.WaspAce]

суббота, 25 мая 2013 г., 19:59:27 UTC+4 пользователь Dimitris Kounalakis написал:

  if not (csDesigning in ComponentState) then
    FHandler := TVCLClientHandler.Create(Self);

This is returned as a memory leak.

Thank you.

I have read description in the cef_life_span_handler_capi (https://code.google.com/p/chromiumembedded/source/browse/branches/1453/cef3/include/capi/cef_life_span_handler_capi.h) and found that 

//If an application provides its own top-level window it should handle OS

// close notifications by calling cef_browser_host_t::CloseBrowser(false (0))

// instead of immediately closing (see the example below). This gives CEF an

// opportunity to process the 'onbeforeunload' event and optionally cancel the

// close before do_close() is called.

// The cef_life_span_handler_t::OnBeforeclose() function will be called

// immediately before the browser object is destroyed. The application should

// only exit after OnBeforeclose() has been called for all existing browsers.

I will fix this soon.

[Architector.WaspAce]

Oh sorry, i can't fix it in the TWAChromium component. You indeed have to intercept form close query in your application as you show above.