ExoPlayer: Exoplayer IMA Extension Memory Leaks and SDK Issue

[REQUIRED] Issue description

Memory leaks and SDK version issue in v2.9.6

[REQUIRED] Reproduction steps

I just started to implement the IMA extension in my application that has a video streaming feature using Exoplayer and everything works fine until a memory leaks appears when closing the app after this implementation even after calling adsLoader.setPlayer(null) in onStop() and adsLoader.relase() in onDestroy(). I am currently using a Single Skippable Inline: https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/124319096/external/single_ad_samples&ciu_szs=300x250&impl=s&gdfp_req=1&env=vp&output=vast&unviewed_position_start=1&cust_params=deployment%3Ddevsite%26sample_ct%3Dskippablelinear&correlator= From the documentation page here: https://developers.google.com/interactive-media-ads/docs/sdks/android/tags

Another thing is it seems like the SDK version is outdated, this is what I saw in a stacktrace whenever I play some video. Invalid internal message, ignoring. Please make sure the Google IMA SDK library is up to date.

[REQUIRED] Link to test content

N/A

[REQUIRED] A full bug report captured from the device

Here is my full stacktrace.txt

[REQUIRED] Version of ExoPlayer being used

Exoplayer dependency v2.9.6

[REQUIRED] Device(s) and version(s) of Android being used

LG K10 K430dsy Android M 6.0.0

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 15

Most upvoted comments

I am also detecting a leak, using leak canary. It seems to be the webview present in adsViewGroup that is not released correctly. Like @ArcherEmiya05, I can confirm that imaAdsLoader.setPlayer(null) and imaAdsLoader.release() are correctly called.

I am also using exoplayer 2.9.6 with IMA 3.11.2 Screenshot_20190524-110153