Avatar of AlHal2
AlHal2Flag for United Kingdom of Great Britain and Northern Ireland asked on

CLR weaknesses and workarounds

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.
.NET Programming

Avatar of undefined
Last Comment

8/22/2022 - Mon

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

Thanks for the detailed answer.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes