I have got a new MT app that seems to crash when memory is constrained. Starting the App I immediately get level 1 memory warnings due to all the other stuff that was running. Run my app for a few minutes and I get ( I assume) a level 2 warning and then all the ViewControllers begin to unload and somewhere a selector is called on a GCd object.
Is this correct behavior - I would assume the OS would try and unload background programs 1st before trying mine?? Is the fix just to comment out base.DidReceiveMemoryWarning (); in DidReceiveMemoryWarning() but would this just create more problems? If not - what what can I do to minimize the chance of a crash and clean up nicely - I have de-registered NSNotification centers during ViewDidUnload() - do I need to remove .Net event handlers as well? Any help or insight in this area would be appreciated. -- View this message in context: http://monotouch.2284126.n4.nabble.com/Memory-issues-running-a-MT-app-when-memory-is-constrained-tp4566980p4566980.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
