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
Am I correct in assuming this loop never wrote out any lines? I've been
trying to recreate this with a simple sample, but the memory size looks
dead stable so far.
Rick
On Wed, Aug 8, 2012 at 5:10 PM, Mark Miesfeld miesf...@gmail.com wrote:
Okay, I put print outs in the SysFile tree code and
Mark,
I'm seeing the same growth with both versions and it looks like it is a
classic memory fragmentation problem. An external call context keeps a
hashtable of all object references it hands out to external functions like
SysFileTree that protects those objects from garbage collection.
On Wed, Aug 8, 2012 at 3:21 PM, Rick McGuire object.r...@gmail.com wrote:
I'm seeing the same growth with both versions and it looks like it is a
classic memory fragmentation problem. An external call context keeps a
hashtable of all object references it hands out to external functions like
