In this video we explore how Xamarin Android handles garbage collection and interacts with the Java garbage collector.
- [Instructor] Xamarin Android and Xamarin iOS…handle memory in very different ways.…To fully understand why a memory leak,…or a crash, happens in a Xamarin Android application,…we need to understand how the mono memory management system…interacts with the underlying Java Platform.…In Xamarin iOS, there is the mono garbage collector…working with the underlying iOS objects…that use reference coding.…In Native Android, however, it sits on top of Java,…which has its own garbage collector.…This means that as Xamarin Android application…actually has two garbage collectors.…
One is the .NET Garbage Collector…that is part of the mono framework.…The other's the native Java Garbage Collector.…Like the .NET objects under the garbage collector,…Java objects are not released until…the Java garbage collector unloads them,…which will happen when it detects…sufficient memory pressure.…The problem with this, is the mono garbage collector…understands what's happening with the .NET objects,…and the Java Garbage Collector understands…
- Working with tuples
- Using C# throw expressions
- Inspecting UI structures with Xamarin Inspector
- Identifying memory leaks in iOS and Android
- Recording and playing back tests with Test Record
- Using embedded assemblies in Android
Skill Level Intermediate
1. C# 7 Language Improvements
Inspecting UI structures3m 34s
4. Test Recorder
5. Embedded Assemblies
Where to go from here1m 54s
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.