Hi Craig,

You talk about "after the 6th double-click and transfer from the 1st window to the 2nd window", but on what are you double clicking ? What does the code do on the double click? What do you mean exactly with "transfer from the 1st window to the 2nd"?

Are you doing an OpenSheet of an already opened window? If that's the case, then be aware that the window's Open() event will still be executed.

Maybe there's some things being CREATEd which haven' been previously destroyed?

regards.

Hi Appeon,

It is as if the memory is not being released after each iteration of the OpenSheetWithParm to the 2nd window from the 1st window.  I know that there is still a connection between the two windows.  Is there a maximum amount of times that the OpenSheetWithParm function can be called from the same two windows?  As I said earlier the 2nd window has at least 100 to 200 data windows being executed including drop down data windows.  I double click from the 1st window to the 2nd window and after 5 or 6 interactions the application flicker and "hangs".  Could it be a timer or resize event?  This application uses PFC and I have migrated those pbl's.  This happened with SAP PowerBuilder and now Appeon.  It doesn't matter if I run it in the IDE or from the VDI using the runtime libraries.  I am attempting to debug the code to see where the problem is but we have a lot going on in the 2nd window. These are two main windows within a MDI Frame.  Any help would be appreciated.  Can we have a Skype call next week to discuss.  Thanks, Craig

Hi Chris,

This application uses the PFC.

This is strange and even stranger still that eventually, the PB App comes back from it's "frozen" state. That sounds like a long running script that finally completes and then returns control to the main application after its completion. Depending on parameters because it is passing a structure there could be 100 data window retrievals (Including drop down data windows) going on in sequence in the second window.

  Can you tell us ....

When you open WindowB from WindowA, does is disable the object that performs the OpenWithParm (ie CB) until WindowB closes?  Yes. What types of Windows are "A" and "B" in my example above in your PB App? Main windows Does this issue happen in the IDE, an EXE or both?  Both. What types of processing is occurring in the two windows you describe? Enabling tabs and Data Window Retrievals

Thanks,

Craig

Hi John,

Greetings, Craig -

Others may disagree, but I don't believe you've supplied us with enough information for us to offer much in the way of practical advice.

What, in general, do these secondary windows do? Are they data entry windows? Reports? Long-running, data-intensive processes? 100 rows of data, 100,000?  They are data retrievals of up to 40 rows but most are one row.  Has each window been closed when you open the next one? No. If they're open, are they idle? Yes. Have you tried monitoring CPU usage, Virtual Memory, Disk Activity (i.e., Task Manager, Resource Monitor) simultaneously to gain any insights? Yes. The CPU Usage goes up.  What O/S are you running the PB app under? Windows 7. Is the application memory constrained? Is the app performing a lot of disk I/O? Yes. Is the app waiting on the database? No. What DBMS does it use? Sybase 15.0. Is it running on Citrix? Virtual Desktop? Does the app interface with 3rd-party software? No third party software and the same issue happens in the IDE or on Citrix.

These are all things that can impact performance. I'm not saying we need answers to all of these questions... but it's nearly impossible to offer useful advice on the limited information you've given us so far.

Regards, John

Hi Craig;

  This is strange and even stranger still that eventually, the PB App comes back from it's "frozen" state. That sounds like a long running script that finally completes and then returns control to the the main application after its completion.

  Can you tell us ....

1. When you open WindowB from WindowA, does is disable the object that performs the OpenWithParm (ie CB) until WindowB closes?
2. What types of Windows are "A" and "B" in my example above in your PB App?
3. Does this issue happen in the IDE, an EXE or both?
4. What types of processing is occurring in the two windows you describe?
5. Where & when does the 2nd Window grab the Parm information?

Regards .... Chris

Greetings, Craig -

Others may disagree, but I don't believe you've supplied us with enough information for us to offer much in the way of practical advice.

What, in general, do these secondary windows do? Are they data entry windows? Reports? Long-running, data-intensive processes? 100 rows of data, 100,000? Has each window been closed when you open the next one? If they're open, are they idle? Have you tried monitoring CPU usage, Virtual Memory, Disk Activity (i.e., Task Manager, Resource Monitor) simultaneously to gain any insights? What O/S are you running the PB app under? Is the application memory constrained? Is the app performing a lot of disk I/O? Is the app waiting on the database? What DBMS does it use? Is it running on Citrix? Virtual Desktop? Does the app interface with 3rd-party software?

These are all things that can impact performance. I'm not saying we need answers to all of these questions... but it's nearly impossible to offer useful advice on the limited information you've given us so far.

Regards, John

This problem also happens with PowerBuilder 12.6 version?

This problem only happens on VDI?

If your answer is yes to both of my questions, then I recommend you consider using PowerClient to replace VDI or modify your code to workaround the issue.