Hi,

I am using EO.WebBrowser 16.0.17.0 in my click once application. One of my user is receiving the below error when she tried to access a form which contains the webview. Below error is from our logs. Can you pls assist me on this

"trace": {
"exception": {
"class": "Exception",
"message": "Child process not ready. nWaitResult = 1"
},
"frames": [
{
"filename": "EO.Internal.je",
"lineno": 101,
"method": "a(System.String A_0, System.Boolean A_1)"
},
{
"filename": "EO.Internal.je",
"lineno": 114,
"method": "a(System.IntPtr A_0)"
},
{
"filename": "EO.Internal.je",
"lineno": 908,
"method": "a(System.String[] A_0, System.String A_1, System.String A_2, System.String A_3, System.String A_4)"
},
{
"filename": "EO.Internal.aqd",
"lineno": 0,
"method": "a(System.String A_0, System.String A_1)"
},
{
"filename": "EO.Internal.awc",
"lineno": 1403,
"method": "e"
},
{
"filename": "EO.WebEngine.Engine",
"lineno": 508,
"method": "Start"
},
{
"filename": "EO.Internal.ck",
"lineno": 40,
"method": ".ctor(EO.WebBrowser.WebView A_0)"
},
{
"filename": "EO.WebBrowser.WebView",
"lineno": 236,
"method": "y"
},
{
"filename": "EO.WebBrowser.WebView",
"lineno": 326,
"method": "b(System.IntPtr A_0, System.Boolean A_1)"
},
{
"filename": "EO.WebBrowser.WebView",
"lineno": 0,
"method": "Create(System.IntPtr hWnd)"
},
{
"filename": "EO.WebBrowser.WinForm.WebControl",
"lineno": 110,
"method": "a(System.Object A_0)"
}

Hi,

Updated the version to 16.0.28.0, but still the same error show up. Can you pls assist on this.

Thanks!!

This is happening on our customers machine. So how to identify which security software is causing this issue. Also are you guys planning to handle this in your next updates. Thanks.

Can MacAffe cause this issue, because my customer has only this security software installed on his machine.

Hi Asad,

There are basically two scenarios for this error:

1. Another program on the system killed our child process immediately after it launches. Some of such programs are visible to the end user (such as a normal AntiVirus program), but some of them are well hidden (such as Digital Guardian);
2. The DLLs are being loaded over a slow drive (such as a slow network drive), thus the child process did not finish loading before the time out expires;

Please check if you have all DLLs locally and try to set this property to true to see if it helps:

http://www.essentialobjects.com/doc/eo.base.runtime.enablelargeaddressspace.aspx

If none of the above helps, we will be happy to look into the customer's computer if you can provide remote access to us. We will need Visual Studio on that system in order to debug the code to find out exactly what's causing the problem.

Thanks!

Hi,

The fact that other program kills our child processes is a mistake on their part. We dynamically create child process and generate native code at run time, some aggressive AntiVirus program can incorrectly conclude that this is a virus/malware thus kills it as they see it.

As to the stack trace difference, if you can tell us the version number of your DLL, we should be able to match it up with our source code and tell you whether the difference is normal or not.

For such issues it's impossible for us to find out the root cause without actually debugging on that machine. So we do not see any other way.

Thanks!

Hi,

You can find our email here:

http://www.essentialobjects.com/forum/test_project.aspx

We would prefer RDP connection but we are open to other connection. You can email us with the details and we can then go from there.

Thanks!