[Mono-dev] Issues with GC due to libgc

[pablosantosluac at terra.es]

>> Ok, but the problem is that ALL memory should be freed, since there
>> are no references to the arrays. Of course you've to invoke GC. The
>> 600Mb in RES is a leak (Virtual Mem will only grow since libgc will
>> never release it, this is another patch Dick has been working on)
> 
> This can easily be explained by memory fragmentation problems.

Miguel, I don't want to drive you crazy but examining and debugging the
libgc code we've found that the pages are kept marked as "used" instead
of free (David can give you more info in case I'm missing anything).
That's why I don't think fragmentation is the problem. If marking were
ok, the entire mem would be freed (as it happens with 64bits mono).


pablo