Millised on erinevate viidete tüüpide erinevused ja kuidas nad töötavad mälu haldamisel?

In memory management in Android (and Java/Kotlin in general), there are different types of references that affect garbage collection:

• Strong Reference: a normal reference to an object. As long as at least one strong reference exists, the object will not be collected by the garbage collector.

• Soft Reference: used for caching. An object with a soft reference will be collected only when memory is low.

• Weak Reference: an object with this type of reference can be collected in the next garbage collection cycle, even if weak references exist. Used for references that should not prevent object deletion.

• Phantom Reference: used to track when an object is ready to be collected but has not yet been collected. Allows performing additional actions after object collection.

Example of a weak reference in Kotlin:

val strongRef = SomeObject()
val weakRef = WeakReference(strongRef)

// If strongRef becomes null, the object can be collected by the garbage collector, and weakRef.get() will return null

Using different types of references helps manage object lifecycle and optimize memory usage.