MaxNativeAdLoaderImpl's Revenue Listener Causing Memory Leak

[ipena-spigot]

MAX SDK Version

13.0.1

Device/Platform Info

Pixel 4 XL - Android 13

Current Behavior

When loading an Ad for a particular AdUnit and selecting a specific network, MaxDebuggerAdUnitDetailActivity gets leaked

This makes it difficult to look into a different Ad-related memory leak

Expected Behavior

Resources / references should be released such that no memory leaks occur

How to Reproduce

• Max Mediation Debugger
• Ads
• View Ad Units
• Select an Ad where the Format is Native
• Bidders
• AppLovin
• Load
• Close Ad after it shows
• Close Activity
• Check for memory leak with Android Studio profiler***

Steps for: Check for memory leak with Android Studio***

• In Android Studio
• Profiler
• Analyze Memory Usage
• Start profiler task
• Click on detected 2 Leaks
• MaxDebuggerAdUnitDetailActivity
• In the Instance tab: MaxDebuggerAdUnitDetailActivity
• References tab
• Show nearest GC root only
• Expand non referent in WeakReference references

Reproducible in the demo app?

Yes

Additional Info

• The memory leak doesn't seem to happen if you don't select a specific network in the Bidders / Waterfall section
• The memory leak happened when selecting other bidders too
• Seems as though MaxNativeAdLoaderImpl is holding on to a reference to revenueListener, which points to MaxDebuggerAdUnitDetailActivity

[mattn02]

Hey @ipena-spigot - thanks for bringing this memory leak up to our attention! We have identified the issue and the fix will be live in our next SDK update. We will notify you in this thread once it has been released.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.