Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am a bit confused about the storage of large objects within the heap.. Like at what size is the object cosidered large? What types are more likely to be treated as large objects?is there any clear fragmentation methods adapted to manage such objects.
This article has a lot of details, although you should be aware of changes coming in .NET 4.5 too.
The only types which are likely to end up on the LOH are strings and arrays – because they’re the only types which can basically be given a size at execution time. I’m not sure it’s even valid to create a type with so many fields that it would end up on the LOH as a single object – it may well be, but I can’t imagine it happening in reality.
According to the linked article, the limit is currently 85,000 bytes. It’s an implementation detail really though – you should rarely need to think about it.