Closed ztanczos closed 1 year ago
Sounds familiar, we have noticed intermittent aborted navigations, possibly related to race-conditions during initialization.
Thanks @pontusn, yes it seems we also had something similar. We re-ordered our initialization logic and the issue disappeared. We suspect that that the ClearBrowsingDataAsync()
call was still running when we triggered the navigation which - in some non-deterministic cases cancelled it.
Description Our users have reported a sporadic issue when an embedded WebView2 fails to render the web content, it just displays a blank page. There is no sign of error messages or exceptions. The WebView2 control seems to be working fine, i.e.: there is a context menu available, DevTools is working but the location is 'about:blank'. Sometimes it takes just one or two restarts to face this issue, sometimes it cannot be reproduced for days.
Version SDK: 1.0.1823.32 Runtime: 114.0.1823.79 and 116.0.1938.62 Framework: WPF OS: Windows 10
Additional info When we enabled chromium logging via additional arguments (--enable-logging --v=1) we see the following entries:
The only suspicious outlier which we don't have in a regular, successful session is this line:
Unfortunately searching the internet with this log entry did not help.
Any help on how to fix or how to further troubleshoot this problem would be greatly appreciated.
Thanks, Zoltan