[Bug 788025] vaapih264enc leaks 1-4 frames of memory

[GStreamer (GNOME Bugzilla)]

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

--- Comment #12 from Hyunjun Ko <zzoon at igalia.com> ---
(In reply to Harvey from comment #8)
> 
> - Start of app
>     - create pipeline: v4l2src -> caps -> valve (drop = true)
>     - start recording:
>         - create encoder bin: 
>              bin[queue, videorate, videoconvert, vaapih264enc, mp4mux,
> fdsink ]
>              - set videorate: skip-to-first=true
>              - set queue:
>                  max-size-buffers = 10
>                  max-size-bytes = 4k*1.5*10
>                  max-size-time = 0
>                  leaky = GST_QUEUE_LEAK_UPSTREAM
>         - add encoder bin to pipeline
>         - link valve to encoder bin
>         - gst_element_sync_state_to_parent(encoder bin)
>         - set valve: drop = false
>         - wait for fdsink to receive data
>     - stop recording:
>         - set valve: drop = true
>         - gst_element_send_event(encoder bin, gst_event_new_eos())
>         - wait for fdsink to receive EOS
>         - gst_element_set_state(encoder bin, GST_STATE_NULL)
>         - unlink valve from encoder bin
>         - remove encoder bin from pipeline
>         - unref encoder bin

I found some leaks but not sure it's the same leak.

Could you try the following:
1. Just once to create encode bin.
2. When start recording, do link, gst_element_sync_state_to_parent, set valve.
2. when stop recording, set valve, eos event, set state to NULL, unlink. (not
remove encode bin)

I found this removed leaks that I found. But still not sure if this would
affect your case.

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