[Bug 793413] msdk: manage mfxFrameSurfaces seperately with other surfacepool.

[GStreamer (GNOME Bugzilla)]

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

--- Comment #17 from sreerenj <bsreerenj at gmail.com> ---
(In reply to Nicolas Dufresne (stormer) from comment #16)
> Review of attachment 369316 [details] [review]:
> 
> ::: sys/msdk/gstmsdkbufferpool.c
> @@ +258,3 @@
>    if (surface->Data.Locked > 0) {
> +    /* We should increase outstanding, but impossible here since it's
> private.
> +     * g_atomic_int_inc (&pool->priv->outstanding);
> 
> Whether you don't ever give back any buffer to GstBufferPool, or give them
> all. Just don't do a mix. For the first case, have a look at PipeWirePool.
> The V4L2 pool way is a just a bad idea.

Thanks for chime in. What do you think about
https://bugzilla.gnome.org/show_bug.cgi?id=793413#c4 ?
(With some changes to avoid infinite looping)

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