-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IMA Extension Memory Leak #4114
Comments
I'd expect the ads loader to be destroyed and free all its resources when the player activity is destroyed, but not when it's just backgrounded. We need to keep state for the IMA SDK in memory while in the background so that it's possible to resume ad playback. Are you seeing that IMA objects have leaked after the player activity's I understand that you're not using the ExoPlayer IMA extension in your app, but this is just a way to reproduce the issue. Are you seeing that objects have leaked after calling Maybe related: we have seen an issue where IMA leaks its |
The issue is easily reproducible in the main demo sample app which uses IMA Extension; PlayerActivity leaks and remains in memory once you serve an ad as explained in my original post. However, the good news is that it seems an IMA issue and not IMA-extension, you can find a response from IMA team confirming it: |
[Internal reference: b/77574091] |
Issue: #4114 PiperOrigin-RevId: 227516509
Issue: #4114 PiperOrigin-RevId: 227516509
This brings in a memory leak fix. Issue: #4114 PiperOrigin-RevId: 230880521
This brings in a memory leak fix. Issue: #4114 PiperOrigin-RevId: 230880521
Issue description
Using IMA Extension and in the sample main demo app, a memory leak happens when you serve a VMAP and quit the player activity during content playback and after ad/pods playback.
In my opinion, it's an IMA problem and managed to reproduce the issue even without an IMA Extension and following exactly their integration guide but according to them they're claiming it's an IMA-Extension problem and not theirs
https://groups.google.com/forum/#!topic/ima-sdk/ZM-WsPL1xdQ
Reproduction steps
https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/124319096/external/ad_rule_samples&ciu_szs=300x250&ad_rule=1&impl=s&gdfp_req=1&env=vp&output=vmap&unviewed_position_start=1&cust_params=deployment%3Ddevsite%26sample_ar%3Dpremidpostlongpod&cmsid=496&vid=short_tencue&correlator=
Link to test content
Provide a link to media that reproduces the issue. If you don't wish to post it
publicly, please submit the issue, then email the link to
[email protected] using a subject in the format "Issue #1234".
Version of ExoPlayer being used
V2.7.3
Device(s) and version(s) of Android being used
Tested on Pixel XL (Oreo 8.1), Xperia XZ (Oreo 8.0) but can be reproduced on any device
The text was updated successfully, but these errors were encountered: