{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 疯言疯语 的问题《Tips/Techniques for tracking down leaks in monotou》','https://www.manongdao.com/q-1250946.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
What are folks using to track down memory leaks? I've managed via code inspection to figure some problems, but I am at a loss to what can I do next / how am I going to manage issues when my program gets bigger. I know what type of object I'm leaking, but I don't know what is keeping it alive.
In windows .NET, I would just fire up SOS in windbg and via a combination of !dumpheap and !gcroot I would be able to find out what was leaking and who was holding live references to the objects that were not getting collected.
MonoTouch 5.2.3 is out today and it has the profiler in it. Very useful!
We are working to integrate the new Mono profiler (http://mono-project.com/Profile) into MonoTouch's user interface to give you access to this kind of information.