IssueTracker

When using the Support library v4, an extra hierarchy of Views is created for each fragment we add.
This is done through the FragmentManager (https://android.googlesource.com/platform/frameworks/support/+/master/v4/java/android/support/v4/app/FragmentManager.java#L888),
This line of code appears twice:
   f.mView = NoSaveStateFrameLayout.wrap(f.mView);

The reason for this is backwards compatibility and it is better explained in the comment header of NoSaveStateFrameLayout which says:
/**
 * Pre-Honeycomb versions of the platform don't have {@link View#setSaveFromParentEnabled(boolean)},
 * so instead we insert this between the view and its parent.
 */

While this is needed pre-honeycomb,
there's no need form post-honeycomb to do this wrapping which cause deeper hierarchies = bad for performance.

A simple
    if (Current-Api < 11) ...
before that line will fix the problem!


          -----
Extended explanation with images can be found here:
http://stackoverflow.com/questions/16774781/why-is-an-extra-framelayout-created-for-fragments

THANK YOU!