Is this a bug in MonoTouch GC?

by

This is an unfortunate side-effect of MonoTouch (who is garbage collected) having to live in a reference counted world (ObjectiveC).

There are a few pieces of information required to be able to understand what’s going on:

  • For every managed object (derived from NSObject), there is a corresponding native object.
  • For custom managed classes (derived from framework classes such as UIButton or UIView), the managed object must stay alive until the native object is freed [1]. The way it works is that when a native object has a reference count of 1, we do not prevent the managed instance from getting garbage collected. As soon as the reference count increases above 1, we prevent the managed instance from getting garbage collected.

What happens in your case is a cycle, which crosses the MonoTouch/ObjectiveC bridge and due to the above rules, the GC can’t determine that the cycle can be collected.

This is what happens:

  • Your ChildViewController has a sayHiButton. The native ChildViewController will retain this button, so its reference count will be 2 (one reference held by the managed CustomButton instance + one reference held by the native ChildViewController).
  • The TouchUpInside event handler has a reference to the ChildViewController instance.

Now you see that the CustomButton instance will not be freed, because its reference count is 2. And the ChildViewController instance will not be freed because the CustomButton’s event handler has a reference to it.

There are a couple of ways to break the cycle to fix this:

  • Detach the event handler when you no longer need it.
  • Dispose the ChildViewController when you no longer need it.

[1] This is because a managed object may contain user state. For managed objects which are mirroring a corresponding native object (such as the managed UIView instance) MonoTouch knows that the instance can not contain any state, so as soon as no managed code has a reference to the managed instance, the GC can collect it. If a managed instance is required at a later stage, we just create a new one.

More Related Contents:

  1. mach_vm_map failed (error code=3)
  2. Xamarin iOS memory leaks everywhere
  3. Hamburger Menu Xamarin Forms (MasterDetailPage)
  4. Global Exception Handling in Xamarin Cross platform
  5. How I can call a javascript function with MonoTouch and vice versa?
  6. How to symbolicate crash/error logs from a Xamarin Forms iOS project?
  7. Write device platform specific code in Xamarin.Forms
  8. How can I publish my Tizen app from Xamarin forms visual studio 2015
  9. Where Is Machine.Config?
  10. How to implement INotifyPropertyChanged in Xamarin.Forms
  11. Add bottom border line to UI TextField view in SwiftUI / Swift / Objective-C / Xamarin
  12. Does G1GC release back memory to the OS even if Xms = Xmx?
  13. Bitmap, Bitmap.recycle(), WeakReferences, and Garbage Collection
  14. How to compare the performance of Android Apps written in Java and Xamarin C#? Anyway to check quantitative data (code & results) [closed]
  15. Can .NET Task instances go out of scope during run?
  16. How to view PDF file using Xamarin Forms
  17. Garbage collection on intern’d strings, String Pool, and perm-space
  18. QML garbage collection deletes objects still in use
  19. How to make long press gesture in Xamarin Forms?
  20. Does WeakReference make a good cache?
  21. How are String and Char types stored in memory in .NET?
  22. Under what circumstances, we need to call GC.Collect twice
  23. Webview and iFrame Video full screen issue
  24. requestAnimationFrame garbage collection
  25. When should I dispose my objects in .NET?
  26. Measuring time spent on GC
  27. Recreate recipient bubble behaviour in Mail.app / Three20
  28. Xamarin Android Finalizer not getting called when leaving the activity to go to another Activity
  29. ExpandableListView with ViewPager combination as its child
  30. Does Python GC deal with reference-cycles like this?

Leave a Comment