search

AppLovin / AppLovin-MAX-SDK-Android

Other
224 stars 101 forks source link

Memory leaks over time #301

Open laurencedawson opened 2 years ago

laurencedawson commented 2 years ago

I'm seeing some pretty bad memory leaks when using the SDK v11.3.3.

Looking in the source for "MaxAdView" I noticed that the view is setup using application context instead of activity context. Is there a reason for this?

Also can we get some clarification on how to properly dispose of an adview. Right now we're calling:

adView.stopAutoRefresh();
adView.setVisibility(View.GONE);
adView.destroy();

Can you please confirm if this is correct.

Thanks

laurencedawson commented 2 years ago

Any word on this?

Performance is totally destroyed when using AppLovin to the point of being unusable.

thomasmso commented 2 years ago

@laurencedawson - What are the specific memory leaks you are referring to? Why would using application context result in more leaks?

laurencedawson commented 2 years ago

We're using the Amazon APS adapter and our users are complaining that over prolonged usage the app grinds to a halt.

The only change we've made is switch from MoPub to Applovin.

Our concern is that even after calling destroy when an Activity is ended we're not tidying up after the ads sufficiently.

thomasmso commented 2 years ago

Amazon APS adapter had some memory leaks that is fixed in the latest v9.4.3.1. Can you please update to that?

laurencedawson commented 2 years ago

Error persists. No issues when using Admob + APS adapter.

thomasmso commented 2 years ago

ok - we'll continue to investigate