troubleshooting Question

CLR weaknesses and workarounds

Avatar of AlHal2
AlHal2Flag for United Kingdom of Great Britain and Northern Ireland asked on
.NET Programming
2 Comments1 Solution586 ViewsLast Modified:
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.

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 2 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 2 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros