1. I was able to identify that SwipeRefreshLayout leak. What was roughly happening was that I was storing a View in an instance variable of the fragment, so when it got replace()'d, it was detached but the fragment instance was still alive on the backstack, so the instance variable was holding onto the view past onDestroyView(). I also eliminated another very similar leak of my RecyclerView.Adapter that was being caused by the data binding class holding onto references in basically the same way. All in all I learned a lot about memory management and lifecycles, so that's good. But it raised one question - I had previously thought that onDestroy() was when a fragment's instance was released, but I recently learned that onDetach() is called after onDestroy(), which implies that I was wrong. (I wouldn't have had those leaks, if the instance were freed in onDestroy()). So when exactly is the instance freed, then, and what exactly happens in onDestroy() if not that?

2. I'm implementing an uncaught exception handler and a routine to let users email me crash logs, like you suggest in your Distribution chapter. You can see the relevant methods here: https://github.com/ajh3/NoSurfForReddit
...