They are created and destroyed at different times, for instance, when putting a fragment on the back-stack. Having two lifecycles for a single screen can be problematic. It’s view’s lifecycle ( onCreateView and onDestroyView).It’s own lifecycle ( onCreate and onDestroy).How do leaks happen in fragments? First, we need to start by reviewing the important nuance of fragments. As a result, this prevents the garbage collector from cleaning up the reference. Let’s establish the type of memory leak this article will discuss.Ī memory leak occurs when an object’s reference is held on to after its purpose has been served.

What is a memory leak?There are many definitions out there.

So, buckle up this may get a little technical. It is geared towards our fellow Android developers as we want to contribute back to the community. This article will go over the memory leak problem and the resolution to the issue. It was a real team effort every developer dedicated time to fix the tools that they own. Eric Klukovich hosted a lunch & learn to spread the knowledge about the issue and the solution to the whole team, who subsequently applied the solution to each affected area of the app. We researched the memory problem and implemented a solution within a week after the initial discovery. The number of crashes was also spread over various devices, and the issue manifested itself in a very inconsistent way.Īs Procore promotes a culture of quality, every Friday, the Android team gets together for Bugsmash Friday, an event dedicated to squashing bugs throughout the app. Early last year, the Procore Android team noticed various crashes in the mobile application caused by insufficient memory. In the world of mobile, there are many resource constraints, memory being one of the most precious.

Android studio fragment backstack