Hi Roland,
I used OxygenBasicProgress of March 29.
Yes, Charles seems to compliment his OxygenProgress with the matching OxygenBasicProgress distros that may contain other WIP files he may wish to update accordingly. I always try to load the both zips and use them together. It practically never fails for me.
Do you see a problematic place in the code, where memory leaks could arise? I am insecure what could be missing.
No, I see no flaws in your code. There seem to be no apparent pitfalls that the memory leak may be attributed to.
Upon some brooding over this phenomenon, I can only say I used to see a similar process memory behavior only in the C++ apps that make use of C++
std::vector facilities. C++ uses its own memory allocation and garbage collection engine, and you can't reallocate or partially free the memory used by its overgrown std::vectors once you don't need the respective vector elements any longer. The C++ memory allocator preserves the memory (though not the objects stored in that memory) just in case you
might need it later. You can only delete the entire std::vector using a
known hack or let it go out of scope and thus get garbage collected.
Which makes me think that the entire MDI engine itself may well be implemented using C++ to take advantage of its template library whereby the MDI child window data would be stored internally to the engine in a set of std::vectors.
