Home
last modified time | relevance | path

Searched refs:ref_mems_count (Results 1 – 2 of 2) sorted by relevance

/third_party/gstreamer/gstplugins_bad/sys/va/
Dgstvaallocator.c102 gint ref_mems_count; member
127 g_atomic_int_set (&buf->ref_mems_count, 0); in gst_va_buffer_surface_new()
330 g_assert (g_atomic_int_get (&buf_copy->ref_mems_count) == 0); in gst_va_dmabuf_mem_copy()
332 g_atomic_int_add (&buf_copy->ref_mems_count, 1); in gst_va_dmabuf_mem_copy()
478 if (g_atomic_int_dec_and_test (&buf->ref_mems_count)) { in gst_va_dmabuf_memory_release()
601 g_atomic_int_add (&buf->ref_mems_count, 1); in gst_va_dmabuf_allocator_setup_buffer_full()
722 g_atomic_int_add (&buf->ref_mems_count, 1); in gst_va_dmabuf_allocator_prepare_buffer_unlocked()
/third_party/gstreamer/gstplugins_bad/
DChangeLog2270 2. We forget to add ref_mems_count, which causes the surface leak because
14345 hold until GstVaBufferSurface's ref_mems_count reaches zero (all the memories