跟踪单道程序泄漏的技巧/技巧？ [英] Tips/Techniques for tracking down leaks in monotouch programs?

问题描述

人们使用什么来跟踪内存泄漏？我通过代码检查来管理一些问题，但是我下一步可以做什么，当我的程序变大时，我将如何处理问题。我知道我正在泄漏什么类型的对象，但我不知道什么是保持活着。

在Windows .NET中，我刚刚启动SOS windbg，并通过！dumpheap和！gcroot的组合，我将能够找出泄露的内容，以及谁正在对未收集的对象进行实时引用。

解决方案

我们正在努力将新的Mono Profiler（http://mono-project.com/Profile）集成到MonoTouch的用户界面中，以便您访问这种信息。

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.

解决方案

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.

这篇关于跟踪单道程序泄漏的技巧/技巧？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！