BriskBard, CEF4Delphi, WebView4Delphi, WebUI4Delphi and WebUI4CSharp

Hi.

Sometimes I have next exception in log file: I want to understand why its happens. How can I debug CEF Delphi?

Hi,

There are some indications to debug CEF4Delphi applications in the 'Debugging' section of this web page :
https://www.briskbard.com/index.php?lang=en&pageid=cef

If the application stops inside Delphi code then it should be much easier to fix thanks to Delphi's call stack and the variable inspector.

However, If it stops inside a CEF DLL call then you can use the CEF debug symbols with the CEF debug binaries. You would need to use "WinDbg" or "Sysinternals Process Explorer" to get the call stack to find the last function that raised the exception.

In any case, you can always post in this forum a screen capture of the Delphi debugger, log copies, etc with the version of Delphi you are using and I'll take a look. Don't forget to say if you are running your app from a local hard drive or a networked unit.

It would be extremely useful to know if this error happens in the latest Delphi version too. The starter edition is free and you can install it in a matter of minutes.

I'm having some random AV too, and then my app crashes. How can i activate this 'log file' ?

Add uCEFConstants to the uses and set these properties in the DPR before the GlobalCEFApp.StartMainProcess call : If you want to add custom error messages in the log use the CefLog or OutputDebugMessage functions from uCEFMiscFunctions.pas

Most of the times you will be getting those AVs because you need to close all the browsers properly before closing your app.
Check the code comments in the MDIBrowser demo.

If your app crashes too often and you had to kill it several times, you may need to delete the cache and cookies directories.

salvadordf wrote: Fri Oct 06, 2017 7:50 pm Add uCEFConstants to the uses and set these properties in the DPR before the GlobalCEFApp.StartMainProcess call :

Code: Select all

  GlobalCEFApp.LogFile              := 'debug.log';
  GlobalCEFApp.LogSeverity          := LOGSEVERITY_ERROR; // use LOGSEVERITY_VERBOSE if you want more details

If you want to add custom error messages in the log use the CefLog or OutputDebugMessage functions from uCEFMiscFunctions.pas

Most of the times you will be getting those AVs because you need to close all the browsers properly before closing your app.
Check the code comments in the MDIBrowser demo.

If your app crashes too often and you had to kill it several times, you may need to delete the cache and cookies directories.

Ok, will do it. In my tests the problem occurs most when i close my app and is triggered on this line :

GlobalCEFApp.Free;

Randomly my app will stop on this line and then freezes on 100% CPU until i force it to close in Task manager. I can see in my app's interface that the browser component disappears, but the app won't close.

Is there anything more i could do to diagnose this issue ?

Thanks !

Hi,

The most common cause of AV errors when you free GlobalCEFApp are unreleased interfaces.
Most of the times that's caused by browsers that were not closed properly but it could also be caused by other CEF interfaces created in your code.

The internal CEF3 structure is very complex and it's not always easy to find what interface is keeping some internal processes alive when you free GlobalCEFApp.

The MDIBrowser, ToolBoxBrowser and TabbedBrowser demos have all the code necessary to close each TChromium safely.

These are the code comments in the TabbedBrowser : The MDIBrowser and ToolBoxBrowser demos wait for all the other child forms to be closed before closing the main form.

If you use the OSR mode you will even have to add a timer after the TChromium destruction before closing the main form.

As I said in my previous message, delete the cache and cookies directories before doing tests.

Hello Salvador,

Thanks for the hints.

My app usually has only one form opened when i close the app ; in this case i need to do something besides make sure there is no child forms opened ?

Another relevant info is that i usually create 3-4 TChromium in my apps, to do different things. Having multiple instances of TChromium could be a cause of issues ?

thefunkyjoint wrote: Sat Oct 07, 2017 2:58 pm My app usually has only one form opened when i close the app ; in this case i need to do something besides make sure there is no child forms opened ?
Another relevant info is that i usually create 3-4 TChromium in my apps, to do different things. Having multiple instances of TChromium could be a cause of issues ?

If you only have 1 TChromium in the main form, it's becoming rarer to get AV errors thanks to all the fixes made to CEF4Delphi with the help of all the forum members.

In your case, it's extremely important to close all the TChromium instances properly before closing your main form.

Please read the code comments in the DPR and PAS files from the previously mentioned demos.
Take a look at the creation and destruction sequences.
Use the demos as a base for your apps if necessary.

I'm still having this issue of the app does not close properly, but what is bothering more is some random AV and crashes of the app during its use, and this did not happen with DCEF3.

I'm activating the verbose logfile to try to find out something.

So far, thank you !

thefunkyjoint wrote: Sun Oct 08, 2017 12:48 pm I'm still having this issue of the app does not close properly, but what is bothering more is some random AV and crashes of the app during its use, and this did not happen with DCEF3.
I'm activating the verbose logfile to try to find out something.

Crashes during its use? That's very unusual.
Are they happening when you free one of the TChromium components?
Maybe a few seconds after you free one of the TChromium?

Try to open that website with this SimpleBrowser :
https://www.briskbard.com/SimpleBrowser.zip

Also try to open it with the official CEF3 Sample Application :
http://opensource.spotify.com/cefbuilds ... nt.tar.bz2