What Xamarin.iOS does with memory management when it compiles C# to native code?

Question

What Xamarin.iOS does about memory management? With usual IL we have Garbage Collector which takes care of objects not in use and reliefs programmer from calling delete. How this works when Xamarin compiles code to native? Who cleans objects which aren't used anymore?

This question answers how compilation works but doesn't explain the memory management part: How MonoTouch works?

Answer 1

The answer you seek was given on the question you linked.

To summarize, the IL-to-native translation process is done ahead of time, but other pieces of the Mono runtime are still required. JIT compilation is only one of the tasks performed by the runtime, and this particular piece is incompatible with iOS' memory restrictions (writable memory pages cannot also be executable, and this is required for a JIT to function). This is, AFAIK, the only reason why ahead-of-time (AOT) compilation is required at all.

The Mono garbage collector does indeed run on iOS, it's just embedded into the binary produced by the Monotouch compiler. The produced binary contains your AOT-compiled application code as well as AOT-compiled versions of the libraries you use, and a slimmed-down version of the Mono runtime.