Hi,

Please try two things:
1. Make sure you are on the latest version;
2. Try to enable EO worker process:

https://www.essentialobjects.com/doc/common/eowp.aspx

There main differences between EO.WebBrowser and Google Chrome browser:

1. The core browser engine for both are based on the same source code --- however EO.WebBrowser is on an older version of Chromium browser engine. Currently EO.WebBrowser is based on Chromium V62. There can be issues in V62 that have already been fixed in newer version thus works fine in Google Chrome browser, which is currently at V70. We are in the process of updating to V70. So if this is the problem, the issue will be resolved after that is done;

2. EO.WebBrowser always runs the browser engine in a child process in 32 bit mode. Google Chrome usually runs in 64 bit mode (on 64 bit OS). This gives it access to much more memory. By default, EO.WebBrowser runs the browser engine through rundll32.exe, which can only use up to 2GB memory. Enabling EO worker process can increase this memory limit to 4GB. So if memory is the issue, then this may resolve the issue for you.

3. Older version does not support software shader. So if you run out of GPU resource then you won't be able to recover. The new version does support software shader as Google Chrome. So make sure you update to the latest build in order to get this feature;

Since you won't be able to try #1 until we have the new release, so please try #2 and #3 to see if it resolves the issue for you.

Thanks!

Hi,

Currently we are looking at end of December/begining of January. We do not have public beta but you can contact us again around that time to check with us to see if we can provide an internal test build to you.

Thanks!

eo: What is the timeline for the next version & can we get started with the internal test build?

Thanks!