Anonymous implementation of okhttp3.Callback

Question

I have recently added a leakcanary to my project to trace the leaks. So during the request to server using okhttp3 I got the leak of 8mb saying that

Anonymous implementation of okhttp3.Callback

So I am wondering is this from the okhttp3 or I am doing something wrong?

Presumably you are performing `apiCall.enqueue(new Callback())` and within this callback you are holding a reference to a activity. — azizbekian, Feb 07 '17 at 05:22
@azizbekian nice catch! I am calling `getActivity()` inside `apiCall.enqueue(new Callback()` — android_griezmann, Feb 07 '17 at 05:41
@azizbekian should I kept the reference out side of `apiCall.enqueue(new Callback()`? — android_griezmann, Feb 07 '17 at 05:41
Would you describe the use case? Why exactly you need to keep reference to activity? What are you performing in callback? — azizbekian, Feb 07 '17 at 05:43
@azizbekian Actually I am using mailLoopper thread of hosted activity inside `apiCall.enqueue(new Callback()` — android_griezmann, Feb 07 '17 at 06:04
If you need to keep reference to the hosting activity, then you have create a custom response class which implements `Callback`, and saving a reference to the activity in a `WeakReference` in order not to keep a hard reference to the hosting activity. — azizbekian, Feb 07 '17 at 06:08

score 2 · Answer 1 · answered Feb 07 '17 at 05:41

2

Presumably you are performing apiCall.enqueue(new Callback()) and within this callback you are holding a reference to the hosting activity.

answered Feb 07 '17 at 05:41

azizbekian

60,783
13
169
249

Anonymous implementation of okhttp3.Callback

1 Answers1