multimedia API 。I find memory leak

using tools : valgrind
==2042== 9,220,736 bytes in 5 blocks are still reachable in loss record 308 of 315
==2042== at 0x4844B88: malloc (vg_replace_malloc.c:299)
==2042== by 0x97FAA87: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x97E3CB7: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x97E7487: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x97FB8AB: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x97FCC3F: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x97FA157: video_parser_parse (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x9717877: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x664B40B: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x4885FC3: start_thread (pthread_create.c:335)
==2042== by 0x605E28F: thread_start (clone.S:89)
==2042== 10,485,760 bytes in 5 blocks are still reachable in loss record 309 of 315
==2042== at 0x4844B88: malloc (vg_replace_malloc.c:299)
==2042== by 0x97F9903: video_parser_create (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x971DF87: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x97BCF0F: NvMMLiteOpenBlock (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x96E35E7: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x96DD51F: ??? (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x96DB5DF: TegraV4L2_Ioctl (in /usr/lib/aarch64-linux-gnu/tegra/
==2042== by 0x48AF6CF: v4l2_ioctl (in /usr/lib/aarch64-linux-gnu/

Please try r28.1. If the issue is still present, please share how to repro it on r28.1.

I have tested by tx1. is TX1 supoort R28.1 ?

TX1 and TX2 both support R28.1. The sample rootfs used is the same, only the driver package for the flash differs…I think JetPack install would be exactly the same since it would download the correct driver package.

Yes. You can install via Jetpack 3.1.

Hi zbit, if you still see the issue on r28.1, please share the steps to reproduce the issue so that we can reproduce it and check further. It may not be easy to get clear information form the partial log you have shared.

i have test in jetpak3.0 version.

Hi zbit,
Which MM API sample do you run and see the memory leak?
Can you try Jetpack 3.1?

Hi zbit,

Have you clarified the cause and resolved the problem?
Any update?