AlHal2

The More I know, the more I don't know

David Johnson, CD

<div>
Thanks for the detailed answer.
</div>


<div>
<div class="content wysiwyg-content">
Where can I find a list of known weaknesses and workarounds of the CLR? &nbsp;I've seen examples below through googling, but was wondering if there is one repository listing these things.<br />
<br />
<br />
One thing I've come across is that no single object can be more than 2GB. &nbsp;A new workaround is in .NET 4.5 called gcGetVeryLargeObjects.<br />
<br />
<br />
Memory Leaks Due to Unused Objects that are Still Referenced. &nbsp;If a program never refers to an object again, but there is some path leading to that object then the Garbage Collector does not release its memory. <br />
Another very well known limitation of .NET is its large object heap. If an object becomes part of this heap, the runtime does not move it. This can lead to a program running out of memory prematurely. When Garbage Collector collects a large object from this large object heap, it can also leave behind holes in the heap, thereby causing the free space to become fragmented. <br />
There are also garbage collection pauses.
</div>
</div>


Where can I find a list of known weaknesses and workarounds of the CLR?  I've seen examples below through googling, but was wondering if there is one repository listing these things.


One thing I've come across is that no single object can be more than 2GB.  A new workaround is in .NET 4.5 called gcGetVeryLargeObjects.


Memory Leaks Due to Unused Objects that are Still Referenced.  If a program never refers to an object again, but there is some path leading to that object then the Garbage Collector does not release its memory. 
Another very well known limitation of .NET is its large object heap. If an object becomes part of this heap, the runtime does not move it. This can lead to a program running out of memory prematurely. When Garbage Collector collects a large object from this large object heap, it can also leave behind holes in the heap, thereby causing the free space to become fragmented. 
There are also garbage collection pauses.

CLR weaknesses and workarounds

Where can I find a list of known weaknesses and workarounds of the CLR?  I&#39;ve seen examples below through googling, but was wondering if there is one repository listing these things.


One thing I&#39;ve come across is that no single object can be more than 2GB.  A new workaround is in .NET 4.5 called gcGetVeryLargeObjects.


Memory Leaks Due to Unused Objects that are Still Referenced.  If a program never refers to an object again, but there is some path leading to that object then the Garbage Collector does not release its memory. 
Another very well known limitation of .NET is its large object heap. If an object becomes part of this heap, the runtime does not move it. This can lead to a program running out of memory prematurely. When Garbage Collector collects a large object from this large object heap, it can also leave behind holes in the heap, thereby causing the free space to become fragmented. 
There are also garbage collection pauses.

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.