StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POEditText causing memory leak
text
Body
copied!<p><strong>Intro:</strong></p> <p>I have an app which has the following structure: ActionBar up top (ActionBarSherlock) ViewPagerIndicator below that (for tabs) ViewPager (hosts Fragments)</p> <p>I have a problem that one of my fragments is causing a rather major memory leak. I narrowed the problem down to the following case:</p> <p>The fragment which is causing the leak does nothing but inflating a layout in it's <code>onCreateView</code> method. This is done the following way:</p> <pre><code>return inflater.inflate(R.layout.filter_auctions_fragment, container, false); </code></pre> <p>Nothing unusual here.</p> <p>The layout file only includes a <code>ScrollView</code>, <code>LinearLayout</code> and two <code>EditText</code>s in it (includes more normally stuff but i narrowed the problem down to just these views to make it simple).</p> <p>Now the code that's used to add the fragment: mTabsAdapter.addTab(tabName, ProblematicFragment.class);</p> <p><code>mTabsAdapter</code> is an instance of <code>TabsAdapter</code>, a class that extends <code>FragmentPagerAdapter</code> of the support library. It's rather standard so I'm not including the source to keep this question as short as possible.</p> <p><strong>Now the funny part:</strong></p> <p>This is what happens with the heap when i rotate my device back and forth a few times:</p> <pre><code>12-28 12:26:27.180: D/dalvikvm(18841): GC_CONCURRENT freed 530K, 7% free 10701K/11436K, paused 4ms+7ms, total 58ms 12-28 12:26:27.180: D/dalvikvm(18841): WAIT_FOR_CONCURRENT_GC blocked 24ms 12-28 12:26:28.270: D/dalvikvm(18841): GC_CONCURRENT freed 737K, 8% free 11048K/11964K, paused 4ms+5ms, total 53ms 12-28 12:26:29.510: D/dalvikvm(18841): GC_CONCURRENT freed 789K, 8% free 11464K/12436K, paused 5ms+5ms, total 42ms 12-28 12:26:30.640: D/dalvikvm(18841): GC_CONCURRENT freed 888K, 9% free 11919K/12984K, paused 4ms+5ms, total 52ms 12-28 12:26:31.810: D/dalvikvm(18841): GC_CONCURRENT freed 903K, 8% free 12421K/13500K, paused 3ms+8ms, total 58ms 12-28 12:26:33.800: D/dalvikvm(18841): GC_CONCURRENT freed 1092K, 9% free 13005K/14272K, paused 4ms+6ms, total 59ms 12-28 12:26:33.800: D/dalvikvm(18841): WAIT_FOR_CONCURRENT_GC blocked 20ms 12-28 12:26:36.000: D/dalvikvm(18841): GC_CONCURRENT freed 1355K, 11% free 13518K/15048K, paused 3ms+8ms, total 74ms 12-28 12:26:36.000: D/dalvikvm(18841): WAIT_FOR_CONCURRENT_GC blocked 19ms 12-28 12:26:38.110: D/dalvikvm(18841): GC_CONCURRENT freed 1450K, 11% free 14106K/15720K, paused 3ms+11ms, total 72ms 12-28 12:26:40.450: D/dalvikvm(18841): GC_CONCURRENT freed 1530K, 11% free 14807K/16516K, paused 2ms+15ms, total 75ms 12-28 12:26:40.450: D/dalvikvm(18841): WAIT_FOR_CONCURRENT_GC blocked 29ms 12-28 12:26:43.030: D/dalvikvm(18841): GC_CONCURRENT freed 1682K, 11% free 15591K/17452K, paused 3ms+10ms, total 66ms 12-28 12:26:43.030: D/dalvikvm(18841): WAIT_FOR_CONCURRENT_GC blocked 32ms </code></pre> <p>Clearly, a memory leak. Yes, i know it causes the Activity to be recreated from the ground up and this is what I want because i have different layouts for landscape and portrait modes. Nontheless it shouldn't cause a memory leak.</p> <p>I've found the source of this problem. It's the two <code>EditText</code>'s that i mentioned earlier. As soon as i remove them from the layout and do the same test (rotate back and forth). These are the GC messages i get:</p> <pre><code>12-28 12:21:41.270: D/dalvikvm(17934): GC_CONCURRENT freed 534K, 7% free 10853K/11576K, paused 3ms+7ms, total 44ms 12-28 12:21:42.560: D/dalvikvm(17934): GC_CONCURRENT freed 818K, 9% free 11113K/12108K, paused 11ms+9ms, total 95ms 12-28 12:21:44.680: D/dalvikvm(17934): GC_CONCURRENT freed 1036K, 10% free 11313K/12528K, paused 3ms+6ms, total 54ms 12-28 12:21:44.680: D/dalvikvm(17934): WAIT_FOR_CONCURRENT_GC blocked 15ms 12-28 12:21:47.420: D/dalvikvm(17934): GC_CONCURRENT freed 1089K, 10% free 11510K/12780K, paused 2ms+6ms, total 79ms 12-28 12:21:47.420: D/dalvikvm(17934): WAIT_FOR_CONCURRENT_GC blocked 39ms 12-28 12:21:50.200: D/dalvikvm(17934): GC_CONCURRENT freed 1317K, 12% free 11461K/12956K, paused 4ms+13ms, total 84ms 12-28 12:21:53.210: D/dalvikvm(17934): GC_CONCURRENT freed 1629K, 14% free 11148K/12956K, paused 3ms+7ms, total 47ms 12-28 12:21:55.580: D/dalvikvm(17934): GC_CONCURRENT freed 1056K, 13% free 11302K/12956K, paused 4ms+7ms, total 59ms 12-28 12:21:57.280: D/dalvikvm(17934): GC_CONCURRENT freed 1306K, 14% free 11200K/12956K, paused 5ms+5ms, total 82ms 12-28 12:21:59.420: D/dalvikvm(17934): GC_CONCURRENT freed 1035K, 12% free 11408K/12956K, paused 3ms+7ms, total 55ms 12-28 12:22:01.990: D/dalvikvm(17934): GC_CONCURRENT freed 1392K, 13% free 11352K/12956K, paused 4ms+9ms, total 54ms 12-28 12:22:01.990: D/dalvikvm(17934): WAIT_FOR_CONCURRENT_GC blocked 30ms </code></pre> <p>Now that's what I want to see!</p> <p><strong>WHY!?</strong></p> <p>Can someone tell my why this is happening? I would like to add that I'm not keeping a reference to these <code>EditText</code> object anywhere in my app (I normally do, but even when i removed all of them for testing purposes the leak still happens).</p> <p><strong>Bonus - MAT Screenshots of the leak:</strong></p> <p><img src="https://i.stack.imgur.com/6fQxw.png" alt="Path to GC Roots (whtout soft/weak refs) for my Activity"></p> <p><img src="https://i.stack.imgur.com/OvnZZ.png" alt="Path to GC Roots (whtout soft/weak refs) for my "ProblematicFragment""></p> <p>As you can see there are 16 instances of the Fragment AND the Activity, while there should be only one.</p> <p><strong>EDIT:</strong></p> <p>I noticed that when i manually add the fragment in a different activity (using <code>FragmentManager.beginTransaction()</code>) the leak does not occur!!! I'm completely confused now...</p> <p><strong>EDIT2:</strong></p> <p>Removing the <code>android:id</code> attribute of the <code>EditText</code>s fixes it... But now they're pretty useless...</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload