This might be a C runtime problem/artifact. Since RexxStart always causes a new thread to be spawned this could be a cleanup issue with the threading lib or internal memory routines.
Just thinking out loud here. David Ashley On 07/06/2009 01:05 PM, Rick McGuire wrote: > Ok, I think this problem might need a different pair of eyes looking > at it or a different approach. I figured out where the handle leak is > coming from and fixed that problem, but there is a memory leak of > about 24-32Kb per call to RexxStart() that's got me completely > puzzled. I've set break points on every place where storage is > allocated or released for this sample program to verify that things > were getting cleaned up correctly and I've not found anything that > looks like the likely cause of the leak. Mark, do you have any > tools/techniques that could be useful here? I find it curious that > the memory grows without consuming any more handles. > > Rick > > ------------------------------------------------------------------------------ > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
