It's very easy to reproduce. Just create 2 activities with ads and switch
back and forth between them... they will not get garbage collected

I posted a Stack Overflow question for 4.1.1 here:
http://stackoverflow.com/questions/7695576/android-admob-4-1-1-has-a-...

This includes a test project for v4.1.1 but it is still relevant because
the bug still exists.

WebRep
Overall rating

This is a real issue. I have this memory leak with orientation changes, as
explained in the stackoverflow page.
Following this page workaround which is to use a static AdView seems to
work, but it is still leaking the original Activity the static AdView is
constructed with
(this parameter):

 mAdView = new AdView(this, AdSize.BANNER, ADMOB_PUBLISHER_ID);

Isn't there a better solution to avoid this huge memory leak ?

Changing orientation 10-20 times in my app is sufficient to trigger an
OutOfMemoryException on
bitmap creation, and at this point 33Mb of native memory is used (!!!),
there is none left.

http://stackoverflow.com/questions/6148812/android-admob-causes-memor...

On Dec 4, 3:16 am, b0b <pujos.mich...@gmail.com> wrote:

You soution probably work, I will try it. It is better than to use a real
Activity which may consume way more memory.

Alternatively I've discovered that destroying the WebView in onDestroy()
greatly reduced the leak (but it still leaks a little):

void destroyWebView(ViewGroup viewGroup) {
        for (int i = 0; i < viewGroup.getChildCount(); i++) {
            if (viewGroup.getChildAt(i) instanceof WebView) {
                WebView view = (WebView)viewGroup.getChildAt(i);
                viewGroup.removeView(view);
                view.destroy();                
                return ;
            }
        }
    }

protected void onDestroy() {
        super.onDestroy();
        ...
       adLayout.removeAllViews();   // admobView view is a child of adLayout
       destroyWebView(admobView);