Rank: Newbie
Groups: Member
Joined: 10/3/2025
Posts: 2
|
Hello EO Support Team,
I am currently using EO.WebBrowser version 25.0.4 in a WPF application targeting .NET Framework 4.5.
I have encountered a consistent issue regarding the WebView.LoadUrl method after the application remains idle.
The Issue: The application functions correctly upon startup. However, if the user leaves the application screen idle for an extended period (approximately 5 minutes or more) without interacting with the browser, the next call to WebView.LoadUrl(URL) fails to perform any action.
Technical Observations:
1. When this issue occurs, I have verified that the WebView.IsReady property still returns true.
2. Despite IsReady being true, calling LoadUrl does not trigger the LoadStarted event, nor does it throw any exceptions. It fails silently.
3. The render process seems to be in a "hung" or "suspended" state, possibly due to OS power management or garbage collection, even though the main WebView object is still referenced in the code.
Environment Details:
EO Product: EO.WebBrowser for .NET
Version: 25.0.4
Framework: .NET 4.5 (WPF)
OS: Windows 10
Question: Is there a recommended setting (such as DisableGPU or specific process management settings) to prevent the child process from becoming unresponsive during idle times? Or is there a specific "Keep-Alive" pattern you suggest implementing to keep the WebView active?
Any guidance on how to recover from this state without fully recreating the WebView instance would be appreciated.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,440
|
Hi, We can't think of any reason that can cause this. You can try to upgrade to the current version and see if the problem still occurs. If it still occurs, you can send us the debug logs and we will then go from there. The current version is 2026 and it uses a different key than your 2025 version. So you will need to go to your license key page to download a new v2026 license key and apply that key first. After that you can follow these steps to collect the logs: https://www.essentialobjects.com/doc/common/collect_logs.htmlAfter you have the log, you can send it to us and we will see what we can find. Thanks!
|