Hi,

EO.WebBrowser creates child processes at runtime. By default it uses Windows system files rundll32.exe to start child process. However rundll32.exe is not built with /LARGEADDRESSAWARE link option:

https://msdn.microsoft.com/en-us/library/wz223b1z.aspx

This will limit the logical address space to the process to 2GB. eowp.exe on the other hand is linked with this flag. So it can use full 4GB address space.

At runtime, EO.WebBrowser will automatically creates eowp.exe if it can not find one. However dynamically creating an exe file and then run it can potentially trigger false alarm from security software. So it is recommended that you ship it with your application so it already exists when your application runs. You can also use this method to override the exe file name/location:

https://www.essentialobjects.com/doc/eo.base.runtime.initworkerprocessexecutable.aspx

For example, you can name the exe file as YourAppChildProcessLauncher.exe, thus making it more obvious to end user that this is used by your application.

Thanks!