Okay, I put print outs in the SysFile tree code and in the loop test
it turns out it is not dynamically allocating memory when running in a
loop. Well, it does allocate 2 buffers but frees them each time.
But, it turns out I wasn't comparing apples to orange running on
64-bit and 32-bit. It seems the memory problem is not in
SysFileTree() but in another portion of the code.
When I first ran the loop test on 64-bit Windows, the test program has
this code in it, (that I removed when I ran it on 32-bit Windows.)
do i=1 to f.0
if \var("f.i")
then do
sw = 1
say "Stem variable f."i "has not been assigned a value."
end
end
The bottom line is, if I take that code out of the base program, when
I run the endless loop of SysFileTree() memory use climbs to around
204,000 MB and then holds steady. If I put that code back in, then
Rexx memory usage keeps climbing, until all usable memory is consumed.
Rick - I'm going to open a tracker item for this so I can attach the
exact Rexx programs I was using. I'll put the details in the tracker
and you can look at it if you have time.
--
Mark Miesfeld
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
