I'm trying to solve a problem with a program written in C# that is
occasionally running out of memory.  While using the CLRProfiler tool, I've
seen that sometimes the .NET framework adds memory to the heap, even though
there are large stretches of free memory available.  It looks like the total
amount of variables allocated on the heap don't change much, but in blobs
that are separated by lots of free space.
I thought that memory was added to the heap only when garbage collection
couldn't free enough space for a new allocation.
Has anyone run into a problem like this before?