Rank: Newbie
Groups: Member
Joined: 10/17/2024
Posts: 1
|
Hi everyone,
We're currently working with Essential Objects to create a browser, based on the tabbed browser example source code in C#. However, we've noticed that when we compile the source code, booting takes an excessively long time on some machines—sometimes over 5 minutes, during which the program seems unresponsive. On other machines, it’s better but still not ideal.
Interestingly, the pre-compiled version of the tabbed browser runs smoothly on all PCs. Does anyone have suggestions to mitigate these long boot times? Once it's running, everything works perfectly.
Thanks for your help!
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,178
|
Hi,
It does take a little while for EO.WebBrowser to start because the browser engine code is compressed inside EO.WebEngine.dll and upon first start, it needs to uncompress and load the code in memory. However 5 minutes seems to be excessive. Typically, this is due to third party security software injecting code scanning/validating module into your process that dynamically scan code when it first loads.
If that's the case then the delay is caused by the security software and we would recommend you to look into that and see if you can somehow whitelist/bypass it. The main difference between the precompiled TabbedBrowser.exe is probably because it relies on eowp.exe to start the child process, which somehow bypassed/expedited the scanning process in your environment. So you can try to enable eowp.exe in your application and see if it works for you. The easiest way to enable eowp.exe is to just copy that file to the same directory as EO.Base.dll. It will be automatically detected and used.
There might be other factors that your security software checks/relies on. For example, it may decide to do an extensive scan if the process is started from one "less trusted" directory and a quick scan if the process is started in a "trusted" directory. We would not know exactly what criterial it uses. However the fact TabbedBrowser.exe works might offer you some clues to help you pinpoint down exactly what triggers the extensive scan and then bypass it.
Thanks!
|