olly 69b4aa9e36 Explicitly null out LoadTask.callback on release ... As highlighted by the ref'd issue, we can end up with memory leaks if Loadable.load implementations take a long time to return upon cancelation. This change cuts off one of the two problematic reference chains. This doesn't do much about the ref'd issue, since there's a second reference chain that's much harder to deal with: Thread->LoadTask->loadable. But since it's easy just to cut this one off, I figure it makes sense to do so. Issue: #4249 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=198735386		2018-06-05 12:30:11 +01:00
..
androidTest	Add SurfaceCapturer base class, and provide the first implementation	2018-06-05 12:19:00 +01:00
main	Explicitly null out LoadTask.callback on release	2018-06-05 12:30:11 +01:00
test	Serialize recursive listener notifications.	2018-06-05 12:20:13 +01:00