On Mon, Jul 6, 2009 at 11:05 AM, Rick McGuire<[email protected]> 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.
I'll take a look at it also. I don't have any tools other than the Visual Studio really. I do have a compatibility testing tool that was designed for testing when moving to Vista. But, it (sometimes) detects things like double free of pointers. It pointed out an ooDialog memory problem to me one time. As I recall it had a lot of different areas. I'll see if it is of any use. I forget the name of it, but it is free from Microsoft. Also, the built-in performance counters might help here. They are a little difficult to set up, but I worked my way through it once before. With the performance counters, if I remember correctly, they might only be of use in detecting that there *is* a memory leak, not pinpointing *where* it is. Since you've already detected the leak, they might not help. -- Mark Miesfeld ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
