Quickly locate the location of specific classes of Android memory leaks

1. Locating memory leaks:

You can use leakcanary: to detect all memory leaks.

There is no way to locate a line based on the error log, but it is not difficult to locate the error as long as you understand the possible causes of the memory overflow.

1. Unreasonable coding, wrong references, such as the handler holding the activity object, but the handler is executing a long-term task, it will cause the activity memory leak.

2. Incorrect use of bitmap, a large number of bitmaps are used but not released, which can easily cause memory leakage.

3. Accessing the database cursor or forgetting to close the data stream will also cause data leakage.

4. The adapter is written incorrectly, and the item is not reused, and the memory will be leaked.

5. Endless loop, infinite recursion will also cause leakage.

If you can't find it, you can use memory analysis tools, AndroidStdio, and Eclipse, or a third party.

A memory leak is a situation where a program fails to release memory that is no longer in use due to an oversight or error.

This is one of the nightmares for C and C++ programmers.

1) Substance: Memory leak does not mean that the memory physically disappears, but that after the application allocates a certain piece of memory, due to a design error, it loses control of the memory before it is released, resulting in a waste of memory;

2) Principle: The key to memory leakage is to record the allocated memory and the operation of releasing memory to see if it can match. Track the lifecycle of each piece of memory;

3) Method: Different development environments have different detection methods, which are introduced below with VisualStudio as an example.

When used in VS, it needs to be added.

#define _crtdbg_map_alloc

#include

The role is to map the malloc and free functions to their debug versions malloc dbg and free dbg, which will keep track of memory allocation and release (valid in debug versions).

crtdumpmemoryleaks（）；

The function will show the current memory leak, that is, the memory leak when the program runs to this line**, and all undestroyed objects will report the memory leak, so let this function be put to the end as much as possible.

1. Locating memory leaks:

You can use leakcanary: to detect all memory leaks.