title: Fragment's onActivityCreated() is called after onDestroy() of Activity
body: <p>Today I noticed a strange behavior in my application. </p>
  
  <p>It happens when I stop my application using Devices view from Eclipse. Can someone explain it? </p>
  
  <p>Why is <code>onActivityCreated()</code> of <code>Fragment</code> called even when <code>Activity</code> is already destroyed?
  <code>MyHomeActivity</code> contains two <code>Fragment</code>s and similar log is generated for both. </p>
  
  <p>Here I am pasting logs for one <code>Fragment</code>. 
  <code>NullPointerException</code> is a secondary problem.</p>
  
  <p>I am surprised why <code>onActivityCreated()</code> is called when the call stack was initiated from <code>onDestroy()</code> of <code>MyHomeActivity</code>?</p>
  
  <pre><code>03-05 12:31:21.414: W/System.err(5638): java.lang.NullPointerException
  03-05 12:31:21.421: W/System.err(5638):     at **MyListViewFrag.onActivityCreated**(BuddyListViewFrag.java:85)
  03-05 12:31:21.421: W/System.err(5638):     at android.support.v4.app.Fragment.performActivityCreated(Fragment.java:1468)
  03-05 12:31:21.421: W/System.err(5638):     at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:931)
  03-05 12:31:21.421: W/System.err(5638):     at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1088)
  03-05 12:31:21.421: W/System.err(5638):     at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1070)
  03-05 12:31:21.421: W/System.err(5638):     at android.support.v4.app.FragmentManagerImpl.dispatchReallyStop(FragmentManager.java:1888)
  03-05 12:31:21.421: W/System.err(5638):     at android.support.v4.app.FragmentActivity.onReallyStop(FragmentActivity.java:787)
  03-05 12:31:21.421: W/System.err(5638):     at android.support.v4.app.FragmentActivity.doReallyStop(FragmentActivity.java:764)
  03-05 12:31:21.421: W/System.err(5638):     at android.support.v4.app.FragmentActivity.onDestroy(FragmentActivity.java:322)
  03-05 12:31:21.421: W/System.err(5638):     at MyFragmentActivity.onDestroy(RbrFragmentActivity.java:57)
  03-05 12:31:21.421: W/System.err(5638):     at **MyHomeActivity.onDestroy**(MyHomeActivity.java:254)
  03-05 12:31:21.421: W/System.err(5638):     at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:2663)
  03-05 12:31:21.421: W/System.err(5638):     at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:2694)
  03-05 12:31:21.421: W/System.err(5638):     at android.app.ActivityThread.access$2100(ActivityThread.java:117)
  03-05 12:31:21.421: W/System.err(5638):     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:968)
  03-05 12:31:21.421: W/System.err(5638):     at android.os.Handler.dispatchMessage(Handler.java:99)
  03-05 12:31:21.421: W/System.err(5638):     at android.os.Looper.loop(Looper.java:130)
  03-05 12:31:21.421: W/System.err(5638):     at android.app.ActivityThread.main(ActivityThread.java:3687)
  03-05 12:31:21.429: W/System.err(5638):     at java.lang.reflect.Method.invokeNative(Native Method)
  03-05 12:31:21.429: W/System.err(5638):     at java.lang.reflect.Method.invoke(Method.java:507)
  03-05 12:31:21.429: W/System.err(5638):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867)
  03-05 12:31:21.429: W/System.err(5638):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:625)
  03-05 12:31:21.429: W/System.err(5638):     at dalvik.system.NativeStart.main(Native Method)
  </code></pre>
  
  <p>I am using support library for providing <code>Fragment</code>s to pre-HoneyComb devices, if that makes any difference.</p>