Hi,

Having multiple child process does not mean they would consume a lot of memory. See here for more details:

https://www.essentialobjects.com/forum/postst8270p2_RunDLL32-and-Memory-Footprint-of-EOWebBrowser.aspx#43275

In short, what you wanted to share is already shared between the multiple child process.

Thanks!

Hi,

We are not aware of any limits about number of WebViews but this does not mean there isn't any or there won't be any. This limit if exists, would be imposed by the Chromium browser engine, not us. And it may also depend on other factors such as amount of resource available on your system. You can think of a WebView as a tab in Google Chrome browser ---- while its generally safe to assume that you can open maybe a dozen tabs, it would not be surprising that the browser will crash/fail if you try to open hundreds of tabs.

The limit that you run into mostly appear to be a pending resource loading limit. The browser engine restricts how many resource can load simultaneously. This limit is designed to be "reasonable" and this can change from version to version. You can observe this limit by using Google Chrome browser to simultaneously download multiple large files, and eventually you will not be able to start new download until some old download completes.

We do not provide direct control to either limit. You maybe able to find some command line argument that can control the concurrent resource loading limit online and you can try to pass such argument to our library through this property:

https://www.essentialobjects.com/doc/eo.webengine.engineoptions.extracommandlineargs.aspx

You can set the above option through this property:

https://www.essentialobjects.com/doc/eo.webbrowser.runtime.defaultengineoptions.aspx

Hope this helps.

Thanks!