Welcome Guest Search | Active Topics | Sign In | Register

Essential Objects Product Support Forum » All Products » Support » Intermittent Blank Screen Issue with EO.WebBrowser Control

Intermittent Blank Screen Issue with EO.WebBrowser Control Options
Previous Topic · Next Topic
Luke Coldiron
Posted: Monday, June 16, 2025 11:18:51 PM
Rank: Newbie
Groups: Member

Joined: 6/27/2015
Posts: 9
I've been using the EO.WebBrowser control in a product for many years, upgrading with many different versions. The latest version I have been using is 25.1.22.0, but I continue to encounter an intermittent issue reported by customers when loading only following webpage: https://www.cjis.gov/nics/PRServletSSO.

At times, the browser control loads only a blank screen, and despite repeated attempts, I have been unable to reliably reproduce the issue. Customers experiencing this problem seem to be affected by something changing on the web server’s end, as the C# control fails to load the URL. However, when they access the page through Chrome or Edge outside the application, it loads without issue.

This problem always resolves itself after a random duration. Sometimes within minutes, other times after hour, causing significant frustration for users who rely on in application functionality. I have a event listener for the LoadFailedEventHandler event, however this event is not raised in this circumstance.

Troubleshooting Request
What logging or diagnostics can I enable to help identify why EO.WebBrowser fails to load this page in this circumstances?

Code Example
The issue occurs regardless of whether the call below is asynchronous or synchronous:

Code: C# 
webView.LoadUrlAsync(url: "https://www.cjis.gov/nics/PRServletSSO", skipCache: false);


Any insights or debugging recommendations would be greatly appreciated.
Back to top
 
eo_support
Posted: Wednesday, June 18, 2025 3:04:42 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,383
Hi,

The issue most likley is related to cache. When you call WebView.LoadUrl, it would check if it has a "fresh" copy in the local cache. If it does, it will load from the cache without fetching from the server. This may cause problem if the cached page does depends on resources from the server which has been updated. In essense, in this case you would have a "mismatch" between the updated server and a cached and out of date client version that do not work together.

One way to avoid this is to always clear cache when application starts, or add a refresh button and call webView.Reload(true) when the button is clicked.

If the problem continues, you can try two things:

1. Use the built-in DevTools to examine to page to see if you can spot anything obviously wrong:

https://www.essentialobjects.com/doc/webbrowser/advanced/debug.html

2. Collect the runtime logs after the problem and send the logs to us:

https://www.essentialobjects.com/doc/common/collect_logs.html

Once we have the logs we can look into it and see what we can find.

Thanks!
Back to top
 


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.