Debugging tools
Knowing what a memory leak and a memory churn are and what strategies we can pursue to avoid them, we now need to know how we can find them and how we can profile our code from a memory perspective.
As we have mentioned several times in this chapter, we must always keep an eye on the amount of heap memory used by our application processes, trying to keep it as low as possible and to free resources as much as possible while checking the garbage collector's behavior. Our application needs to be able to stay together with other applications on devices with the most varied amounts of RAM. Therefore, keeping that in mind, we will focus on helpful tools able to analyze the memory usages and we will know how to read common logs related ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access