My Account |  Site Map | Contact Us  
 The same content in Microsoft HTML help file format is included in the download package.
Using eowp.exe

Both EO.Pdf and EO.WebBrowser dynamically create child processes and run browser engine inside the child process at runtime. By default, Windows system file rundll32.exe is used to create the child processes. Using this method has the following limitations:

  • rundll32.exe is not compiled with /LARGEADDRESSAWARE compile option, as such it can only use maximally 2GB of address space instead of 4GB address space. You may receive this runtime error:
    One of the child processes used by EO components reported an out of memory error. 
    If your system has sufficient memory, please consider setting EO.Base.Runtime.EnableEOWP to true.
  • Third party AntiVirus/Security software can often raise false alarm for using rundll32.exe thus causes EO.Pdf/EO.WebBrowser to fail;

You can avoid these limitations by following these steps:

  1. Set EO.Base.Runtime.EnableEOWP to true when your application starts;
  2. Distribute eowp.exe (found in the installation folder) along with your application. You should place this file in the same directory as EO.Base.dll;

This will create child processes using eowp.exe and reduce the chances of both receiving out of memory error and being incorrectly terminated by third party security software.

Alternatively, you can call EO.Base.Runtime.InitWorkerProcessExecutable to create eowp.exe dynamically. This method allows you to customize the name and the location of the executable, which can be helpful to reduce the potential confusion to the end user, or make it easier to set up whitelist for AntiVirus application.

Direct link to this topic