Problems with the Component in Load event

[adilsonpazzini]

When I use the component in a form only, and ask to load any site, it works normal, but when I try to use it with a secondary form, it gets looped, calling the executable itself several times and does not load anything into the component.

Example: I made a small project, where an initial form opens and it contains a button that calls another form that contains the Chromium component and I ask to open it, to load some website, at that moment, instead of loading the site, it is calling the itself executable, non-stop.

If anyone can help me thank you

Environment - LAZARUS 1.8.4 with CEF4 version - 3.3029.1619 of 05/12/2017.
System Operation - Windows7 32Bits.

since ha gradeço

Adilson Pazzini

[adilsonpazzini]

Print from a simple example screen with just a form1 in the design.

[adilsonpazzini]

Now the example with a project with 2 forms, and one as main form calling the second

[adilsonpazzini]

teste.zip

Follow example for test

[dliw]

By default CEF is initialized by the TChromium component. This works fine as long as the browser component is loaded when the program is started (i.e. is on the main form) or if a subprocess executable is used.

You do not use a subprocess executable. In this case CEF uses the main application as subprocess (see the section SubProcess in the readme for more information). However, in your case this fails, because CEF is not initialized on program startup - and the application gets fully loaded.

There are two possible solutions:

1. use a subprocess executable (this is the preferred way)
2. quick fix: call CefInitialize as early as possible, e.g. in the Initialization section of your main form. The downside to this is, that CEF always gets initialized even if it is never used.

[adilsonpazzini]

Thank you very much, it worked.

You say that if using with the CefInitialize option would not be very good, why? Well, I'll have to use it this way, because the other one by external call, aesthetically, it will not be good for me.

[dliw]

A seperate subprocess is how CEF is supposed to be used. One of the reasons is memory consuption. The subprocess usually is much smaller in size than the main application. Startup time of the subprocess may be another reason.

Also as I said, calling CefInitialize early means that CEF is initialized, no matter if it is used later or not and increases startup time.

[adilsonpazzini]

Okay, thank you so much for returning.