Hello,

I've created a UserControl with a Browser in VB.NET and registered it using "Make COM visible" and "Register as COM interop".

Now I'm consuming this UserControl in VB6.
This works very fine at first, but after a few calls to "LoadUrl"...

Try
_webView.LoadUrl(value)
Catch ex As Exception
MessageBox.Show(ex.Message.ToString())
End Try

... the Browser simply becomes plain white without any error message.

The problem can be reproduced almost immediately when I don't only use LoadUrl(), but when I first call LoadUrl(), then navigate manually to another webpage, for example by clicking a link on a webpage and then calling LoadUrl() afterwards.

All properties still seem to be valid. For example,

Try
Return _Browser.WebView.Url
Catch ex As Exception
Return String.Empty
End Try

returns the correct URL.

Memory consumption seems perfectly fine, btw.
For testing purposes, I added a label inside my NET UserControl so that I can check if my UserControl entirely crashed.
But when the white-out appears, the label is still visible, so the UserControl didn't crash entirely.

I think the problem is isolated to the Browser.

Can you please advise what else I can check? Is there an error log to be found somewhere?

EO.WebBrowser.dll 17.1.76.0

Hi EO Support,

I am also facing the same issue.
the web view is loading the first url but not showing it on control and if url is redirected to another page it is also not firing the web view load complete event.

Please update once you solve this issue.

Thanks,
Tank

Hello Tank,

The original issue is specifically related to classic VB6. So your issue would be a completely different issue. Please try to create a test project and send the test project to us. Once we have that we will investigate further. See here for more details on how to send test project to us:

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

Thanks!

Hi EO Support,

the issue is not solved in our production environment :(
i will submit test project. please look at it at earliest as this is being escalated.

Regards,
Ashish

Thanks. We will look into the test project as soon as possible.

Hi,

We have tried your test project both with version 16.2.23.0 and the current version. We are not able to reproduce in either versions.

There are a number of issues that MAY causes the problem you observed. One of the most common reason for such issues are related to your display driver and hardware acceleration. A buggy display driver that claims to be capable of doing certain hardware acceleration but doesn't do it right can cause such problems. The easiest way to verify whether this is the problem is to turn the hardware acceleration off by setting Runtime.DisableGPU to true. If this eliminates the problem for you, then it's almost certain that the problem is caused by display driver.

There are also other issues that have been fixed on our end that can cause this problem. To verify if those are the issues, you can try the latest build and see if it resolves the issue for you. We did try both the version you mentioned and the current build and we do not see any difference here though. So this may not be the problem.

Thanks!