[Bug 797159] Significant memory leak in (at least) omxh264enc and omxmjpegdec on Raspberry Pi

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=797159

--- Comment #4 from Nicolas Dufresne (ndufresne) <nicolas at ndufresne.ca> ---
(In reply to benwolsieffer from comment #3)
> I figured out what was wrong with my valgrind setup and was able to get this
> leak report (note that the pipeline was only running for a short time, so it
> didn't leak that much memory):
> 
> ==14223== Process terminating with default action of signal 2 (SIGINT)
> ==14223==    at 0x4BCFE34: _Exit (in
> /nix/store/b6b0lfsn1wqhsinvy078i1b1vhi96fqs-glibc-2.27/lib/libc-2.27.so)
> ==14223== 
> ==14223== HEAP SUMMARY:
> ==14223==     in use at exit: 2,315,683 bytes in 20,885 blocks
> ==14223==   total heap usage: 101,153 allocs, 80,268 frees, 230,807,468
> bytes allocated
> ==14223== 
> ==14223== Thread 1:
> ==14223== 100 bytes in 1 blocks are possibly lost in loss record 7 of 31
> ==14223==    at 0x4847AD0: malloc (vg_replace_malloc.c:299)
> ==14223==    by 0x649C813: vcos_generic_mem_alloc_aligned
> (vcos_mem_from_malloc.c:56)
> ==14223==    by 0x64646B7: vcos_malloc_aligned (vcos_mem_from_malloc.h:68)
> ==14223==    by 0x64646B7: vc_vchi_cec_init (vc_vchi_cecservice.c:236)
> ==14223==    by 0x645B473: bcm_host_init (bcm_host.c:115)
> ==14223==    by 0x577485B: gst_omx_core_acquire (gstomx.c:129)
> ==14223==    by 0x577B8FF: gst_omx_component_new (gstomx.c:781)
> ==14223==    by 0x578EDD7: gst_omx_video_enc_open (gstomxvideoenc.c:749)
> ==14223==    by 0x5573DDB: gst_video_encoder_change_state (in
> /nix/store/wx5wjmlkfp8k32hqq26wby5i2jigwzbf-gst-plugins-base-1.14.3/lib/
> libgstvideo-1.0.so.0.1403.0)

This one can be ignored, it's system setup, ran once.

> ==14223== 
> ==14223== 108 bytes in 14 blocks are possibly lost in loss record 8 of 31
> ==14223==    at 0x48479D8: malloc (vg_replace_malloc.c:298)
> ==14223==    by 0x484A4DF: realloc (vg_replace_malloc.c:785)
> ==14223==    by 0x49F5943: g_realloc (in
> /nix/store/l8wanykgzg5h18axlvv0nnicc0a40las-glib-2.56.0/lib/libglib-2.0.so.0.
> 5600.0)

I'm guessing you are missing glib symbols, or the glib is build with
-fomit-frame-pointer, this stack trace give no information. Pretty small
though.

> ==14223== 
> ==14223== 240 bytes in 1 blocks are possibly lost in loss record 9 of 31
> ==14223==    at 0x4847AD0: malloc (vg_replace_malloc.c:299)
> ==14223==    by 0x649C813: vcos_generic_mem_alloc_aligned
> (vcos_mem_from_malloc.c:56)
> ==14223==    by 0x649BC9F: vcos_malloc (vcos_mem_from_malloc.h:53)
> ==14223==    by 0x649BC9F: vcos_dummy_thread_create (vcos_pthreads.c:637)
> ==14223==    by 0x84BA03B: vcos_thread_current (vcos_platform.h:370)
> ==14223==    by 0x84BA03B: ilcs_execute_function_ex (vcilcs.c:800)
> ==14223==    by 0x84BAE53: ilcs_execute_function (vcilcs.c:833)
> ==14223==    by 0x84BBB7B: vcil_out_get (vcilcs_out.c:239)
> ==14223==    by 0x5775A23: gst_omx_component_get_parameter (gstomx.c:1133)
> ==14223==    by 0x5776BFB: gst_omx_port_update_port_definition
> (gstomx.c:1328)
> ==14223==    by 0x5776C9B: gst_omx_port_is_enabled (gstomx.c:2508)
> ==14223==    by 0x578218B: gst_omx_video_dec_loop (gstomxvideodec.c:1569)
> ==14223==    by 0x49343F3: gst_task_func (in
> /nix/store/iqw3lnskbqrhg8l0sdpj9wimsl4ac8zp-gstreamer-1.14.3/lib/
> libgstreamer-1.0.so.0.1403.0)

Would need to study vcos code, also small.

> ==14223== 
> ==14223== 492 bytes in 4 blocks are possibly lost in loss record 13 of 31
> ==14223==    at 0x484A490: realloc (vg_replace_malloc.c:785)
> ==14223==    by 0x49F5943: g_realloc (in
> /nix/store/l8wanykgzg5h18axlvv0nnicc0a40las-glib-2.56.0/lib/libglib-2.0.so.0.
> 5600.0)
> ==14223== 
> ==14223== 1,008 bytes in 6 blocks are possibly lost in loss record 15 of 31
> ==14223==    at 0x484A228: calloc (vg_replace_malloc.c:711)
> ==14223==    by 0x40121DF: allocate_dtv (in
> /nix/store/b6b0lfsn1wqhsinvy078i1b1vhi96fqs-glibc-2.27/lib/ld-2.27.so)
> ==14223== 
> ==14223== 1,628 bytes in 43 blocks are possibly lost in loss record 17 of 31
> ==14223==    at 0x484A228: calloc (vg_replace_malloc.c:711)
> ==14223==    by 0x49F58D3: g_malloc0 (in
> /nix/store/l8wanykgzg5h18axlvv0nnicc0a40las-glib-2.56.0/lib/libglib-2.0.so.0.
> 5600.0)
> ==14223== 
> ==14223== 210,528 bytes in 51 blocks are possibly lost in loss record 28 of
> 31
> ==14223==    at 0x4847AD0: malloc (vg_replace_malloc.c:299)
> ==14223==    by 0x649C813: vcos_generic_mem_alloc_aligned
> (vcos_mem_from_malloc.c:56)
> ==14223==    by 0x648213F: vcos_malloc (vcos_mem_from_malloc.h:53)
> ==14223==    by 0x648213F: alloc_msgbuf (vchiq_lib.c:1753)
> ==14223==    by 0x648213F: completion_thread (vchiq_lib.c:1528)
> ==14223==    by 0x649B357: vcos_thread_entry (vcos_pthreads.c:144)
> ==14223==    by 0x4B0EFE3: start_thread (in
> /nix/store/b6b0lfsn1wqhsinvy078i1b1vhi96fqs-glibc-2.27/lib/libpthread-2.27.
> so)

Vcos thread.

> ==14223== 
> ==14223== 1,110,432 bytes in 269 blocks are definitely lost in loss record
> 31 of 31
> ==14223==    at 0x4847AD0: malloc (vg_replace_malloc.c:299)
> ==14223==    by 0x649C813: vcos_generic_mem_alloc_aligned
> (vcos_mem_from_malloc.c:56)
> ==14223==    by 0x648213F: vcos_malloc (vcos_mem_from_malloc.h:53)
> ==14223==    by 0x648213F: alloc_msgbuf (vchiq_lib.c:1753)
> ==14223==    by 0x648213F: completion_thread (vchiq_lib.c:1528)
> ==14223==    by 0x649B357: vcos_thread_entry (vcos_pthreads.c:144)
> ==14223==    by 0x4B0EFE3: start_thread (in
> /nix/store/b6b0lfsn1wqhsinvy078i1b1vhi96fqs-glibc-2.27/lib/libpthread-2.27.
> so)

Another vcos thread, with a bigger leak, maybe the one. So far, it looks like
you'll have to file a bug against vcos.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.