We are testing the webbrowser control to analyze websites. We think that there is a problem calling the loadURL function to multiple instances of webbrowser control at once. Some of the URLS are not checked since the failed event is raised with The request was canceled error message.

When we check the program with one instance of webbrowser control it works properly.

Our solution consists of several webbrowser controls which were added to a stack panel in a WPF main window.
Each webbrowser control is assigned to a list of URLS. for each webbrowser the LoadURL function is called , after the complete or the failed event and , the loadURL is called again with a new URL from that list. The WPF window is hosted in a windows service process.


We are checking with the latest version.

any suggestions?

We think that the problem was solved. The next call was from the load_complete or load_failed event , Because the webview was still busy in the previous request the current was canceled .We activated the loadURL with a timer and checked the webview.isloading but that was not sufficient. So we added our own flag. In the success, failed event we reset our flag , we also check the isLoading propery before calling the loadURL again. If a request took too long we called the WebView.StopLoad() and reset our flag.

We tried the service to work for some time it worked properly for a day ,after that we got timeout logs for all our requests , (The webview did not respond to new calls (failed or success event were not called)). We are using the trial version to check to component

do you have a cap on the number of requests in the trial version?

thanks

Thanks for the update. That makes perfect sense. IsLoading is primarily for UI purpose (for example, to display a spinning animation when the loading is in progress), so it is updated asynchronously and is not accurate. On the other hand, LoadCompleted and LoadFailed can be used to track LoadUrl reliability.

The trial version does have a cap on the number of requests. After that LoadUrl will stop working. You will need to restart your app in order to reset the cap.

Thanks!