Rank: Newbie Groups: Member
Joined: 8/22/2020 Posts: 4
|
We are distributing to very large audience (more than 100K).
We are using Eo.WebBrowser v 20.2.34 (last one) and Eo.WebBrowser.Winform v 20.2.34, on a Winform .NET 3.5 Application.
We already disabled the use of the component on Windows XP and Windows Vista because otherwise the component crashes with "unsupported operating system".
However, after only 3 days of distribution, we have already collected around 60 customers complaints, reporting mainly three problems:
1) Very common (53 over 60 complaints): When the component loads, after a couple of seconds, it turns completely black. We also tried to give them a very simple app made only with a single WinForm, with a EO.webcontrol and a EO.webview. When the form shows, the EO.Webcontrol turns black and stays black. Trying to open a url by using webView1.Url - takes around 20 seconds of loading (where it normally should take 1), and, after that, a webView1_LoadCompleted is thrown. We are able to read the source by using webView1.GetSource(), so the network part seems fine. It seems just a very serious rendering problem.
2) A few (5 over 60): The component crashes with a very long debug info which (of course) customers doesn't know how to send to us, apparently beginning all with "EO.Internal.dobc`3.aqdi()"
1) Less few (2 over 60): The component crashes together with our App (even if we do have try - catch everyhere).
Affected operating systems, so far:
Microsoft Windows 7 Professional (64 bit) (but NOT ALL of them) Microsoft Windows 7 Home Premium (64 bit) (but NOT ALL of them) Microsoft Windows 7 Ultimate (64 bit) (but NOT ALL of them) Microsoft Windows 8 (64 bit) (but NOT ALL of them)
We tried by installing exactly the same version of operating systems on a Virtual Machine, but we are not able to replicate the problem. Comunication with customers is very complicated and hard.
From our experience, 60 users sending emails means for us the problem is around 100x more, so we expect 6.000 customers having this problem (again, this is against over 100K, so it's a 6%).
We are still trying to investigate.
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,217
|
Hi,
We have just responded your email with some suggestions (I believe you have already tried a few of them). There is one more thing you can try which we will send you in a separate email.
Thanks!
|
Rank: Newbie Groups: Member
Joined: 8/22/2020 Posts: 4
|
I wish to thank EO email Support, which was very useful and quick.
Just for everybody to know, the problem of the "black screen" was related to some GPU rendering.
It can be fixed by using:
EO.WebBrowser.Runtime.DefaultEngineOptions.DisableGPU = true;
And needs to be called before using the component.
Best Regards.
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,217
|
Thank you very much for sharing! Please feel free to let us know if you run into any other problems.
|