Large Object Heap Fragmentation

by

The CLR uses the LOH to preallocate a few objects (such as the array used for interned strings). Some of these are less than 85000 bytes and thus would not normally be allocated on the LOH.

It is an implementation detail, but I assume the reason for this is to avoid unnecessary garbage collection of instances that are supposed to survive as long as the process it self.

Also due to a somewhat esoteric optimization, any double[] of 1000 or more elements is also allocated on the LOH.

More Related Contents:

  1. Implementing IDisposable correctly
  2. What strategies and tools are useful for finding memory leaks in .NET?
  3. .NET Memory issues loading ~40 images, memory not reclaimed, potentially due to LOH fragmentation
  4. What causes memory fragmentation in .NET
  5. Memory leak in Data Access layer using enterprise library
  6. Setting Objects to Null/Nothing after use in .NET
  7. Does using “new” on a struct allocate it on the heap or stack?
  8. WPF CreateBitmapSourceFromHBitmap() memory leak
  9. Attempted to read or write protected memory. This is often an indication that other memory is corrupt
  10. Is a memory leak created if a MemoryStream in .NET is not closed?
  11. Is there any benefit of using an Object Initializer?
  12. Memory Leak in C#
  13. Weak event handler model for use with lambdas
  14. C# memory address and variable
  15. High memory consumption with Enumerable.Range?
  16. Explicitly freeing memory in c#
  17. LOH fragmentation – 2015 update
  18. Initial capacity of collection types, e.g. Dictionary, List
  19. How is memory allocated for a static variable?
  20. How do I get .NET to garbage collect aggressively?
  21. Memory Leak when using DirectorySearcher.FindAll()
  22. Memory limitations in a 64-bit .Net application?
  23. Channels with CancellationTokenSource with timeout memory leak after dispose
  24. Large Object Heap Compaction, when is it good?
  25. C# dictionary – one key, many values
  26. Discovering derived types using reflection
  27. System.Net.WebClient unreasonably slow
  28. Using HashSet in C# 2.0, compatible with 3.5
  29. Explanation of Func
  30. Repository Pattern, POCO, and Business Entities

Leave a Comment