On Wed, Oct 19, 2011 at 3:22 AM, Sergio Fadda <[email protected]> wrote: > Hi Jeff, > > thanks for the reply. > > Unfortunately the issue is present even if I click the button once; I said > "variable number of times" because sometimes it is needed one click, and > sometimes more clicks to replicate the issue.
Ah! I'm sorry, I had misunderstood... > However, doesn't NSOperationQueue mantain a... queue? If so, every instance > of NSOperation should be referenced during the execution and removed from > the queue only when the operation finish... I guess! Yes, it does... but the problem is the it's the ObjectiveC code that holds a pointer to C# memory but the GC doesn't know that ObjectiveC is still using it, so it frees it. This is a source of a lot of confusion among MonoTouch users and one of our top runtime guys is working on figuring out a way to make this work more seamlessly. > > Anyway, I tried to maintain my own NSOperation list that I populate before > adding the operation to the NSOperationQueue and the issue is still there! Okay, then it sounds like my original guess is wrong :-( I've created a new project and added your code to see if I can figure out what the real issue is, so far it has proven difficult. Jeff _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
