1. Roland Smith
  2. PowerBuilder
  3. Wednesday, 17 January 2024 17:57 PM UTC

PB 2022 Build 1892 on Windows Server 2019 run via RemoteApps.

Multiple customers are reporting occasional aborts like this:

The application is MDI style. The background of the frame window has a tab control which hosts multiple WebBrowser controls. The controls display simple HTML developed by our documentation team.

A year ago we moved from PB 2019 to PB 2022 and I swapped out the IE WebBrowser control for the built-in WebBrowser control.

Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 17 January 2024 21:04 PM UTC
  2. PowerBuilder
  3. # 1

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.

 

Comment
  1. Roland Smith
  2. Wednesday, 17 January 2024 21:10 PM UTC
Thanks. I'm leaning towards insufficient memory on the server. They have SQL Server and RDS on the same virtual server running Windows Server 2019.

When I run the app on my laptop, it has 7 instances of pbcefclient.exe running.
  1. Helpful
  1. Miguel Leeuwe
  2. Wednesday, 17 January 2024 21:17 PM UTC
Yw,

yes I've noticed that too. The cef seems to run multiple instances. I don't think it's very solid and I'm not too sure about the new webview2 either. Glad we, at our company don't have to use it so far.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 17 January 2024 18:57 PM UTC
  2. PowerBuilder
  3. # 2

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

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.