Camera memory memory leak analysis (III)

         adopt Provider、sysinfo A mechanism to monitor for memory leaks has some advantages and disadvantages , It can not accurately reflect the corresponding memory The change of , Prefer to choose to pass dumpsys meminfo Go to check Specific process of memory Changes , and dumsys The information will be more comprehensive 、 It is more conducive to the overall control of relevant problems .

One 、Profiler VS dumpsys

        dumpsys memory The amount of information received and the amount of processes that can be monitored are far more than Profiler, Some questions can be answered through dumpsys Find out , Some questions passed Profiler It may be a miscarriage of justice .

Profiler Real time monitoring memory situation ：

dumpsys Under surveillance memory situation ：

 

Two 、 dumpsys meminfo normal 、 Abnormal data comparison

Normal data :

Abnormal data :

 

  3、 ... and 、 Exhibition information platform malloc Anomaly tracking

        Different platforms have certain right malloc Application and release tracking mechanism , Take zhanrui platform as an example , Configure tracking malloc Of backtrace after , Under a device that duplicates a memory leak dump native heap Information , With the platform development The following heap can be obtained by parsing the relevant scripts malloc Stackable lib Information .

 

 

  summary

        Actually Android Memory related problems are not just memory leaks , In the project, I have also encountered the problem that the heap space exception of dynamic application causes the program to crash when using this stack , Two different algorithms in the same project encountered similar problems at the same time , In the end, this question will be applied in advance malloc The space solution solves , But as R & D , I feel that it is really necessary to further study what happened behind these problems , However, the study of this problem may be delay.