Do you know that .NET GC now equipped with yet another option to Compact Large Object Heap. This has been a long problem for people where LOH can produce fragmentation in memory or when Free space table cannot handle allocation requests. LOH is the Large object Heap allocated generally for large objects which are above 85,000 bytes long. The number has been considered as a result of performance tuning. When object allocation requests are made above this threshold, the object is allocated in LOH.
I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.
Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.
Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.
This article is related to
</ span>C#,.NET,Architect,Intermediate,VS2010,.Net,Articles,Computer Tutorials,Daily .Net Tips,LargeObjectHeapCompaction,.NET Garbage Collection,Garbage Collection
</ span>C#,.NET,Architect,Intermediate,VS2010,.Net,Articles,Computer Tutorials,Daily .Net Tips,LargeObjectHeapCompaction,.NET Garbage Collection,Garbage Collection
0 Comments