Tips / methods for tracking leaks in monotouch software?

What do people use to track memory leaks? I managed to check the code to understand some problems, but I am at a loss what can I do next / how will I manage problems when my program gets bigger. I know what type of object I was leaking, but I do not know what supports it.

On Windows.NET, I just run SOS in windbg and with a combination! dumpheap and! gcroot. I could find out what was happening and who made live links to objects that were not collected.

+3
source share
2 answers

We are working to integrate the new Mono profiler (http://mono-project.com/Profile) into the MonoTouch user interface to give you access to this information.

+4
source

MonoTouch 5.2.3 was released today, and it has a profiler. Very helpful!

0
source

All Articles