Ayende @ Rahienhttp://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Kevin Dente commented on Patterns for reducing memory usageSure, but AddMemoryPressure assumes a priori knowledge of the size of the objects. Not very practical in the general case. It's one of the nasty flaws in the whole COM interop story. http://ayende.com/4347/patterns-for-reducing-memory-usage#comment8http://ayende.com/4347/patterns-for-reducing-memory-usage#comment8Tue, 05 Jan 2010 18:52:40 GMTAyende Rahien commented on Patterns for reducing memory usageKevin, That is why you have GC.AddMemoryPressure http://ayende.com/4347/patterns-for-reducing-memory-usage#comment7http://ayende.com/4347/patterns-for-reducing-memory-usage#comment7Tue, 05 Jan 2010 18:43:49 GMTKevin Dente commented on Patterns for reducing memory usageAnother fun one is the scenario with small managed objects managing large unmanaged objects. COM interop is the primary example. When you have large COM objects being used from managed code, the garbage collector isn't aware of that memory usage and doesn't trigger garbage collection. http://ayende.com/4347/patterns-for-reducing-memory-usage#comment6http://ayende.com/4347/patterns-for-reducing-memory-usage#comment6Tue, 05 Jan 2010 17:35:50 GMTJon commented on Patterns for reducing memory usageMinor code fix: "results" should be "result" in your garbage spewer example. Threw me off for a second. http://ayende.com/4347/patterns-for-reducing-memory-usage#comment5http://ayende.com/4347/patterns-for-reducing-memory-usage#comment5Mon, 04 Jan 2010 20:11:16 GMTAyende Rahien commented on Patterns for reducing memory usageFero, I am not really worried about that particular example, I am talking about the general case. http://ayende.com/4347/patterns-for-reducing-memory-usage#comment4http://ayende.com/4347/patterns-for-reducing-memory-usage#comment4Sun, 03 Jan 2010 09:06:40 GMTFero commented on Patterns for reducing memory usageGarbage spewers (quick fix) public string Concat(string[] items) { StringBuilder sb = new StringBuilder(); foreach (var item in items) { sb.Append(item); } return sb.ToString(); } http://ayende.com/4347/patterns-for-reducing-memory-usage#comment3http://ayende.com/4347/patterns-for-reducing-memory-usage#comment3Sun, 03 Jan 2010 08:59:56 GMTAyende Rahien commented on Patterns for reducing memory usagePet, String is immutable, as such, a new string is generated every time we concat the string. http://ayende.com/4347/patterns-for-reducing-memory-usage#comment2http://ayende.com/4347/patterns-for-reducing-memory-usage#comment2Sun, 03 Jan 2010 06:43:25 GMTPet commented on Patterns for reducing memory usageReally interesting article. But, I did some test and found that Code sample above posted doesn't create garbage in the foreach loop. string gets finalized only when we return from the function. Please help with this example. http://ayende.com/4347/patterns-for-reducing-memory-usage#comment1http://ayende.com/4347/patterns-for-reducing-memory-usage#comment1Sun, 03 Jan 2010 05:37:11 GMT