Also, I solved this with my custom dialog view controllers by overriding the
handle constructor, e.g.:
public MyDialogViewController(IntPtr handle): base(handle)
{
}
You might want to check the classes that are having these exceptions to see
if you have overridden these constructors. Try to replicate first with the
simulator by simulating a low memory warning, then override constructors.
I wasn't aware that this was required after receiving a memory warning, but
I believe it will solve a problem I was having in my app. Hopefully it will
help you too.
Cheers
John
--
View this message in context:
http://monotouch.2284126.n4.nabble.com/Any-idea-what-this-could-be-tp4657461p4657484.html
Sent from the MonoTouch mailing list archive at Nabble.com.
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch
