Using the CLR Profiler<\/a> (screenshot above), you can easily see where you are wasting memory (well, it can be scary the first time you see it but in fact, it’s easy). I nearly removed all my runtime allocations with this tool, here are the few tips that can be useful:<\/p>\n 1. Be careful with the class string<\/strong><\/em><\/p>\n String is allocating memory every time it returns a new string. StringBuilder<\/a> is the key to the problem. I didn’t even know what StringBuilder was before working on memory and now I use it everywhere I need to take care about memory. There are some awesome tips (and source code) about StringBuilder on Gavin Pugh’ blog<\/a>. Especially this<\/a> and this<\/a>. You have everything you need now \ud83d\ude42<\/p>\n 2. Reuse your lists<\/strong><\/em><\/p>\n I had multiple sections of code creating a temporary List<> in order to add elements to need a special treatment. This was in an update function in my case. It is handy and fast to write code like that, but it allocates memory. To fix this, I know have the List<> as a member of the class. I clear<\/a> it and reuse it when needed. When creating a list, you should use the constructor with an int<\/a> used to define the default capacity of the list. (List<Vector2> l = new List<Vector2>(64) for instance).<\/p>\n 3. foreach loops<\/strong><\/em><\/p>\n I converted my foreach loops in C++ like for loops and it saved me some allocations. Memory allocated due to foreach loops on lists is showing up in the CLR Profiler as System.Collections.Generic.List<T><\/em>.<\/p>\n Conclusion<\/strong><\/em><\/p>\n I hope you’ll find this useful. In Spring Up Harmony, I still have some run-time allocations, mostly in the particle engine, when a new fx is launched (I use Mercury<\/a> for now). However, it seems that the garbage collector is not causing hick-ups therefore I’m ok with it.<\/p>\n![\"clrprof\"](\"http:\/\/www.frozax.com\/blog\/wp-content\/uploads\/2010\/05\/clrprof.jpg\" "\\"clrprof\\"")
<\/a><\/p>\n