|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello, Over time, we've noticed that there are some sites that when loaded, the WebView goes blank (seems to crash) and a new one has to be created. This can be reproduced each time and therefore, one is not able to view the page. Here is an example URL: http://www.investopedia.com/terms/b/basispoint.aspAs soon as the page loads, the WebView goes blank. This happens when running on Windows Server 2012 R2 when running under Remote Desktop.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, Please update to the latest build and follow the steps here to see if that resolves the issue for you: http://www.essentialobjects.com/doc/common/large_address_space.aspxThanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello,
We've already enabled the large address space and distribute the worker process since we use it on large pages. We're running version 15.3.43.0, so I'll try updating to 2015.3.78.0 and see if that addresses the issue.
I do want to note that the website usually works on a Windows 10 machine, but crashes on Windows Server 2012 R2 running in remote desktop. We have error handling in place and the WebView doesn't throw an exception, but when calling a method on the WebVIew, then we receive an exception that it's been destroyed.
Thank you for you help.
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello,
Just checking in again to see if there is any update on this issue. I've updated to the most recent version of EO again and still seeing the same issue.
Thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
Please download EO.Total 2016 from our download page. This issue is fixed in this release. Note that this is the 2016 release, so it requires a different license, which you can get from your license key page since your subscription is still valid.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello,
We've updated to the latest and are still having the same issue. When running the application under RemoteApp/Remote Desktop, the WebView immediately crashes, web page goes blank, and no exception is thrown. I can't reproduce when running the application locally, only when running it in a RemoteApp/Remote Desktop session.
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, Please try this Url and see if you see the same behavior as Google Chrome browser: https://test.webrtc.org/The issue we fixed in fact does not really have anything to do with remote desktop sessions --- it has to do with whether your computer has any video/capture devices. The correct behavior for the above Url is that it will display an error message with error code DeviceNotFoundError when the computer does not have any capture devices. However the old version will not display this error which triggers other errors and eventually crash. This issue is fixed in the new version. Please let us know if you can see the correct behavior on your end. You can also double check EO.WebBrowser version by loading "chrome://version" in the address bar. This will show you EO.WebBrowser and Chromium version. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello, Using "chrome://version", I verified the version of EO (16.0.7.0) and Chromium (49.0.2623.28). Going to that URL locally, https://test.webrtc.org/, I start the test and it gets stuck at "Network->Tcp enabled". When running this in RemoteApp, WebView crashes at "Network->Tcp enabled" with no exception. I ran the example tabbed browser locally and that seem to complete without issues. Is there something that needs to be handled for WebRTC? Our application is a WinForm app, not WPF. I then ran the example tabbed browser in the Remote Desktop session and it crashed as well. Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
Did you see the "DeviceNotFoundError" message? You should see this message both in Chrome browser and in EO.WebBrowser.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello,
Yes, I do see the "DeviceNotFoundError" message. I click "Continue without Audio and/or Video", run the test, and that's when it crashes.
Running Chrome, the test runs to completion without crashing.
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
Please download the latest build (2016.0.17.0) from our download page and see if it resolves this issue for you. We have tested this build here and it works fine.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello,
The latest version fixes the issue locally and no longer freezes on WebRTC test. The WebView still crashes with no exception when running the test if the application is running in a Remote Desktop Session/RemoteApp.
To add a little more info, when running in RemoteApp, this application is hosted in a High-Availability Remote Desktop Services deployment on Amazon Web Services.
Thank you.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
In that case is it possible for you to provide a test environment for us so that we can investigate further? Also you may want to run Google Chrome in the same environment and see if you experience the same problem as well. If Chrome also has the same problem, then we will usually wait for Chrome to fix it first since we are not in a position to fix issue existed in the Chrome browser engine.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello,
We could definitely work to get you access to our test environment. What kind of access would you need to investigate further? Our current environment that we run in gives very little access to the end-user, so we might have to enable some things to allow you to debug.
Also, just verified that running Chrome in this environment works without an issue on the WebRTC test.
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
If you can provide remote desktop access to one of your test environment it will be very helpful for us to investigate this problem because that would allow us to see everything and upload test DLLs.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
We have found an issue that can cause the crash. Please download build 2016.0.28.0 from our download page and see if it resolves the issue for you.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello,
This is great! Just tried it out now and it no longer crashes. The test still seems to get stuck at TCP, but that's not currently an issue for us.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Thank you very much for confirming the fix. Can you provide more specific on what you meant by get stuck at TCP? We ran the test page with our TabbedBrowser sample and we got the exactly same result as Chrome browser.
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
When I was first testing it out, when the test got to Network -> TCP Enabled, it would just stay there and not complete the test. I chalked it up to our proxy as a possibility as the tabbed browser worked fine. I now no longer have that issue. so it's all looking correct!
Thank you again!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Great. Thanks for confirming!
|
|