Hi Roland;

  The only thing that I can think of is that for the R2 build's built-in Web Browser control it used the "Chromium" web engine vs the R3 release that uses the WebView2 web engine. I wonder if this is a Chromium browser engine issue?  Just a guess at the moment of course.

Regards .. Chris

Not the same bug, but who knows if it might solve your problem:

From our application object's Open event:

// 18/06/21: seems to be a necessary setting for CEF webbrowser control:
int li_ret
string ls_ret
li_ret = WebBrowserGet("UserAgent", ref ls_ret)
if ls_ret = "" then
	li_ret = WebBrowserSet("UserAgent", "AppeonWebBrowser")
	if li_ret <> 1 then
		Messagebox("Information", "Error setting the UserAgent for the WebBrowser", information!)
	end if
end if

// 05/07/21: avoid an existing Appeon bug of blowing up when using the webbrowser control on Windows Server 2012 R2:
open(w_wbrowser_dummy)
close(w_wbrowser_dummy)

There was a bug on Win server 2012 when closing the application. The "w_wbrowser_dummy" window is a simple popup window that's set to invisible. It avoided the crash when closing powerbuilder.