Hi François,

Maybe someone in the community might be able to point out if there are any cons to using this Windows API, but

SetProcessWorkingSetSize(-1, -1, -1) helped with freeing memory usage for a PB Windows Service application I did some way back.

Cheer,

Ricardo

Hi Benjamin

my guess was it was all pointers when it came to objects but one of my coworkers kept bothering me on the subject so I told him I'd ask.

we completly missed that section of the help, I feel embarrassed because the help section is usualy my first stop.

thank you for your answer

Hello François.

Does readonly argument versus by value make a difference ?

In a some of our service objects arguments for objects are by value where they should be by reference (because those objects are modified) but even if they're passed by value they're still correctly modified. The resaon they're passed by value is because I can't do a my_service_object.of_function(this) when calling it from let's say my master datawindow.

Does that have an impact on memory management. And what would be the correct way to do things ?

When you pass objects to a function, what you're actually passing is a pointer variable. The method changes the type of pointer you get; "by reference" passes the actual pointer to the object in memory, "by value" passes a copy of the pointer, and "read-only" passes a read-only copy of the pointer. (PB being written in C++ I can take a guess at what happens behind the scenes: by reference passes a variable holding the actual address in memory, by value passes a variable with a pointer to the original address in memory, read-only passes a const pointer to the address)

In all three cases, the state of the original object can change. However only when using "by reference" can you change the original pointer to point to a different object. I.e. let's say of_function(ref n_object o) creates a new object of type n_object and assigns it to "o" -> o will now point to the newly created object instead of the object that was passed to it. The only reason to use "by reference" is if you want to reassign a different object.

You can also reassign the passed-in pointer when you pass "by value" but the original pointer will not change in this case, the newly created object will only be available within the method. In "read-only" mode, you cannot reassign the pointer at all.

This is the reason "my_service_object.of_function(this)" will not compile if you pass by reference; "this" is a read-only pointer and can never be reassigned to point to another object.

Source: https://docs.appeon.com/pb2019/powerscript_reference/ch06s06.html

In conclusion, whatever method you're using should not have any effect on memory, it's basically just pushing around pointers.

Hi thanks for the answers

Thanks Mike for the links for the tickets

some more informations about that we do use a lot of openUserObjects

I build our framework like a blank canvas where almost everything is created on the fly as needed. When I red the tickets it hit me that it was what I was facing, but I also red that this was supposed to be fixed in build 2353 which is the one we're using.

I'll still investigave and test some more towards that.

Chris

the 1) is in place since the beggining, I think I got that one from some of your old posts.

Blob usage is minimal but I'll give it a whirl once I finished with the arrays.

We do not use tab contrôls but I'll keep it in mind.

thanks for the advices.

François

Hi François;

  You seem to have done some great work to try and reduce the App's overhead!

  For the App "minimize" (aka MDI Frame) - that trick used to work back in the PB 10.x / 11.x and early 12.x builds of PB.  I used to use that trick in my STD Framework but I noticed by PB 12.6 that this no longer had a memory releasing effect.  :-(

  Other things that I do in my framework are ...

1) DataWindow Control Destructor event (preferably in a DC ancestor) ...

• THIS.Reset ()
• THIS.DataObject = ""
• Yield ()

2) Memory release for large arrays of any variable types, for example ...

• Blob   lblb_data[]
• Blob   lblb_null []
• SetNull (blb_null )
• //FOR NEXT LOOP using lblb_data array
• // More processing using lblb_data array
• lblb_data  = lblb_null   // Free memory at end of processing

3) Tab controls ... try to always use "CREATE on Demand" property ON

HTH

Regards ... Chris

i've seen problems too with openUserObject, but it seems to max out after awhile.  That doesn't help your RDP situation, but at least it doesn't seem to grow until it crashes

bug reports that are related to memory usage (not being released)

https://www.appeon.com/standardsupport/search/view?id=4479

https://www.appeon.com/standardsupport/track/view?id=5242