Aggressive GC for WeakReference on Android starts from 2.3

[Gwindor]

I read RxAndroid sources a bit and when I reached this classes (https://github.com/ReactiveX/RxAndroid/blob/0.x/library/src/main/java/rx/android/functions/ViewAction1.java) I start worried about how using WeakReferences can afect application on real device and production application. Also weak refereces used in more important place like this (https://github.com/ReactiveX/RxAndroid/blob/0.x/library/src/main/java/rx/android/operators/OperatorViewClick.java)

Here is a reason (http://developer.android.com/training/displaying-bitmaps/cache-bitmap.html#memory-cache, note section).

[ronshapiro]

What's there to be worried about? The aggressiveness of GC doesn't change the fact that when a GC pass occurs, the object being referenced by the WeakReference is either referenced in other locations or not.

[ronshapiro]

That link says that weak/soft references are bad for caches, but here we explicitly don't want to hold on to our reference for longer than we need it.

[mttkay]

What @ronshapiro said. This has nothing to do with caching but with not accidentally leaking Context.

@Gwindor let me know if that addresses your concerns!

[JakeWharton]

Closing. Comment if you have more concerns or open a new issue.