跟踪单点触控程序中的泄漏的提示/技术? [英] Tips/Techniques for tracking down leaks in monotouch programs?

问题描述

人们用什么来追踪内存泄漏?我已经通过代码检查设法解决了一些问题，但是我不知道下一步该怎么做/当我的程序变大时我将如何管理问题.我知道我正在泄漏什么类型的对象，但我不知道是什么让它保持活力.

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.

在 windows .NET 中，我只需在 windbg 中启动 SOS，并通过 !dumpheap 和 !gcroot 的组合我将能够找出泄漏的内容以及谁持有对未收集对象的实时引用.

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.

推荐答案

我们正在努力将新的 Mono 分析器 (http://mono-project.com/Profile) 集成到 MonoTouch 的用户界面中，以便您可以访问此类信息.

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屋！