TDA4VM：A72 linear decrease in total memory during aging

Hi,

Please add the details in English. Are you suspecting memory leaks? If yes please mention the SDK version that you are using & the steps to reproduce.

- Keerth

After running the software for 2.2 hours, X began to grow linearly and ran out of memory for about 10 hours, resulting in node1 exiting; Throughout the entire process, there was no significant increase in memory for each process;

Multiple tests have found that the growth time of X has been basically consistent, around 2.2 hours after operation

By shielding the module, when only starting eda+driving (DataSource+side view), X will also start to grow after running for 2.2 hours

The X calculation formula can be derived as follows: MemTotal=MemFree+[Lab+VmallocUsed+PageTables+KernelStack+HardwareCorrupted+Bounce+X]+[Active+Inactive+Unevicetable+(HugePages_Total * Hugepagesize)]

HI  expert：

SDK Version:ti-processor-sdk-rtos-j721e-evm-07_02_00_06

Yes, it is suspected to be a memory leak. The A-core meminfo statistics show that memory is decreasing, but the memory of the process is not significantly changing. Instead, it is decreasing, as shown in the following figure. Is there any means to investigate this problem?

Again what's the use case? How to reproduce this issue? Are you using vison_apps?

Please share the steps to reproduce.

Regards,

Keerthy 

Xiaoyi, what's your mean by 'X' under the items of /proc/meminfo? is the memory used increasing and memory free decreasing and all others kept unchanged?

Can you also upload two pictures to demonstrate the trend of memory leakage by /proc/meminfo or free/top/htop commands as well please?

thanks. 

meminfo(1).txt

HI liu

 Txt is the data counted to meminfo. The limit is run time is 550 and Memory leak begins.

 During runtime, MemTotal remains unchanged, corresponding to a larger used in free m, but the process's physical memory does not grow

Xu,

What's the use case?

Regards,

Keerthy 

HI 

 We did not use official use cases, it is our own app, mainly for camera and algorithm functions

Okay. It is hard to catch memory leaks when we have the top level information. Do you use encode/decode?

- Keerthy