Hi Thierry,

Did this issue occur after you used WebBrowser Control in your application?
If yes, the issue is with sharing the UserDataFolder of Webbrowser(WebView2). This is a known issue and I suggest you work it around as follows:
Workaround 1:
If running exe in different directories, you can work it around by setting different UserDataFolder:
For example, set UserDataFolder in the Open event of the Application:
String ls_path
ls_path = GetCurrentDirectory( )
WebbrowserSet("UserDataFolder", ls_path )

Workaround2:
When you run the exe in the same directory, copy the exe and rename it to work around. Renaming the exe is also a way of implementing different UserDataFolder. By default, the Webbrowser sets Temp\{appname}+UDF as UserDataFolder.

Regards,
Ken

experienced same strange behaviour after migrating to PB2022 R2.
A client reported that launching a long process on an instance of my powerbuilder application and let it run, he opens a second instance of the same .EXE to do other stuff but it freezes until the first .EXE finishes its task. Never happened before. We resolved for now by tweaking the long process to make it finish quicker.

Hi Thierry;

  How is the 2nd instance of the App launched?
Regards .. Chris

Hi, Thierry -

What DBMS vendor, version, etc. are you using, and what are the transaction object’s properties?

I’m wondering if this is a MARS-related (Multiple Active Result Set) issue?

Best regards, John

You can use the taskmanager, resource monitor or processExplorer to check which process is blocking/locking your app or make your app for it to finish. For example, I've seen several times some kind of system printspooler causing problems in the past.

Sorry I can't be more specific, no time.

regards

following....

I checked the bug reporting site:  https://www.appeon.com/standardsupport/newbug

and i've seen nothing.  this is a pretty big issue for use of the webbrowser control.  I assume this problem still exists in R3?

For our part in my company we have just installed PB 2022 R3 and we have an application that runs nightly processes, we see that we are getting what is described here.

Specifically a process takes 15 minutes with the PB 2022 version, now with the PB 2022 R3 version it exceeds 3 hours, it does not finish and creates a ghost instance of the executable.

Does anyone have a solution or give me a hint to solve it?

Now we have the old executable and we are discarding the use of PB 2022 R3.

Best regards.

We have the same problem in my company that you detail: @Thierry Del Fiore

The user runs 2 times the same application to perform different work actions that do not overlap each other. Now with the executable made in PB 2023 R3 Build 3289 while in the 1st instance of the application runs a process the 2nd instance of the application is blocked, no action can be performed.

We restore a backup copy of the executable generated with PB 2022 Build 1892 and this way of working works perfectly without blocking.

This seems to be a bug with this new version of PB

Does anyone know a way to fix it?

Everything stated here by different users I have checked and we continue with the problem.

Thanks for your help.

Does this problem persists, even if we don't use web browser control?

Need to know as we have planned to go-live a project developed / migrated in PB 2022 R3.  Many users do open multiple instances of the same exe in the machine, where performance should be good.

We don't use Webbrowser control in that project so far, but planning to go for that in a couple of months.

Happiness Always
BKR Sivaprakash