Hi, I'll try to create a simple test that reproduces the problem as soon as possible. >Also, as a test, could you initialise the memory stream to roughly the size required to store the entire list<T> and see if it works then. That works fine if I do it that way. But my problem is that I can't really know in advance how much memory the serialization will use, so it's not really a viable solution. I'm thinking of trying to split up my list into smaller chunks to see it this could fix the problem by avoiding the large object heap, if there is such a heap in mono. Jonathan
_____ De : Alan McGovern [mailto:[EMAIL PROTECTED] Envoyé : Thursday, May 10, 2007 10:40 AM À : Jonathan Gagnon Cc : [email protected] Objet : Re: [Mono-list] Too many heap sections: Increase MAXHINCR orMAX_HEAP_SECTS (meant to send this to the list aswell) Hi, If you could create a simple testcase that fails, it'd make life much easier. I.e. create a small .cs file which creates a similar List<T> and then serialises it. This makes fixing the problem easier as we don't have to write our own testcase which may or may not hit the problem. Also, as a test, could you initialise the memory stream to roughly the size required to store the entire list<T> and see if it works then. Alan
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
