[Bug 762543] xvimagesink: wrong pool selection when rendering buffers having GstVideoCropMeta attached

[GStreamer (GNOME Bugzilla)]

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

--- Comment #5 from Nicolas Dufresne (stormer) <nicolas.dufresne at collabora.co.uk> ---
For the reference:

commit df313a6dbc563cd4922f9897316516b760738ba4
Author: Nicolas Dufresne <nicolas.dufresne at collabora.co.uk>
Date:   Fri Jun 5 14:30:12 2015 -0400

    xvimagesink: Don't share internal pool

    Sharing the internal pool results in situation where the pool may have
    two upstream owners. This creates a race upon deactivation. Instead,
    always offer a new pool, and keep the internal pool internal in case
    we absolutely need it.

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

So the pool created in set_caps() is only used for when upstream buffer are not
using the proposed pool. I'm not sure how you get a miss-match in video_info
here. Are you using an upstream pool with a size that does not match the one
allocated in the caps ?

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