Rank: Newbie
Groups: Member
Joined: 9/9/2026
Posts: 1
|
Hi. We have a problem, when using EO.WebBrowser in a WPF app, the browser acts very slow, with no apparent cause. The CPU or RAM use isn't high or anything, it's just super unresponsive.
This is the case both for loading the webpage, and for interacting with the webpage. I.e it takes around 30 seconds to load a page, and when the page has loaded, you can hover the mouse over a link and it takes like 20 seconds before the mouse cursor changes to the hand and the link is clickable.
When using any other browser, like edge or firefox, the page loads and acts quickly like normal, so it's not a problem with the PC or website. Another browser object, like System.Windows.Controls.WebBrowser, also works fine. So it's just EO.WebBrowser.
This is with v22.2 (I don't have license to newer versions). But I have also tried 22.1 and 22.0 without significant changes. I have tried various other options like EnableEOWP and CachePath = "" too.
How can I troubleshoot this?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,516
|
Hi,
There are many different scenarios that can cause performance issues. But there is no "magic" option on the WebBrowser control that can significantly improve performance. So the key is to find out what triggered it.
First you would want to identify whether its related to the web page or it is slow with any page. If it is related to a specific web page, you can then try to modify the page to see if you can see what triggered it. One possibility is it has JavaScript code that relies on features only existed in newer browser engines thus would fail/fall into a different code path in older browser.
Another common situation is a third party security software is dynamically scanning/intercepting EO.WebBrowser code. To verify this, you can try to run the same application on a clean Windows installation without any additional third party applications. If that works fine, then it most likely has to do with something else on your system.
If you continue to have problems, you will need to try the current version and see if it works for you. You do need a new license to use the current version, but it would also allow you to continue receiving support. We provide tech support for one year after the purchase so technically you are no longer eligible for support based on your previous license.
Thanks!
|