Like the docs say, think about it this way. If you were to do an application like a book reader, you will not want to load all the fragments into memory at once. You would like to load and destroy Fragments as the user reads. In this case you will use FragmentStatePagerAdapter. If you are just displaying 3 "tabs" that do not contain a lot of heavy data (like Bitmaps), then FragmentPagerAdapter might suit you well. Also, keep in mind that ViewPager by default will load 3 fragments into memory. The first Adapter you mention might destroy View hierarchy and re load it when needed, the second Adapter only saves the state of the Fragment and completely destroys it, if the user then comes back to that page, the state is retrieved.

Like the docs say, think about it this way. If you were to do an application like a book reader, you will not want to load all the fragments into memory at once. You would like to load and destroy Fragments as the user reads. In this case you will use FragmentStatePagerAdapter. If you are just displaying 3 "tabs" that do not contain a lot of heavy data (like Bitmaps), then FragmentPagerAdapter might suit you well. Also, keep in mind that ViewPager by default will load 3 fragments into memory. The first Adapter you mention might destroy View hierarchy and re load it when needed, the second Adapter only saves the state of the Fragment and completely destroys it, if the user then comes back to that page, the state is retrieved.

FragmentStatePagerAdapter:

使用FragmentStatePagerAdapter，您不需要的片段是 摧毁。事务提交时完全删除 fragment从你的活动的FragmentManager。 FragmentStatePagerAdapter中的状态来自于它 将从savedInstanceState保存你的片段的Bundle什么时候 它被摧毁了。当用户导航回来时，新的片段将是 使用片段的状态恢复。

FragmentPagerAdapter:

相比之下，FragmentPagerAdapter什么也不做。当 不再需要这个片段。FragmentPagerAdapter调用 detach(Fragment)而不是remove(Fragment)。 这个destroy是片段的视图，但留下了片段的实例 在FragmentManager中存活。创建的片段 FragmentPagerAdapter永远不会被销毁。

FragmentPagerAdapter存储以前从适配器获取的数据，而FragmentStatePagerAdapter每次执行时都从适配器获取新值。

不知道技术细节，但根据我的经验: 如果你尝试在一个片段中的viewPager中使用FragmentStatePagerAdapter，那么你的子片段的选项菜单可能会被搞砸(或者根本不显示)，如果你导航到另一个页面并返回。但是它将与FragmentPagerAdapter一起工作。 据我所知，在用户单击一个选项卡之前，子片段的onCreateOptionsMenu没有被调用。这可能是有意的，但对我来说是一场噩梦。

在毫无希望的搜索中，我偶然发现了一些页面: https://issuetracker.google.com/issues/37092407 Viewpager片段的选项菜单显示彼此的按钮 嵌套片段在viewpager与不同的菜单

PS:任何使用FragmentStatePagerAdapter的优雅解决方案或建议都是受欢迎的

在文档或本页的答案中没有明确说明的事情(即使由@Naruto暗示)是，FragmentPagerAdapter将不会更新片段，如果片段中的数据发生变化，因为它将片段保存在内存中。

所以即使你有有限数量的片段显示，如果你想要能够刷新你的片段(例如你重新运行查询来更新片段中的listView)，你需要使用FragmentStatePagerAdapter。

我在这里的全部观点是，片段的数量以及它们是否相似并不总是需要考虑的关键方面。你的片段是否是动态的也是关键。