Skip to content

msdk: use cached response for DMABuf when the frame size is same

User is seeing corrupted display when running videotestsrc ! video/x-raw,format=NV12,width=xxx,height=xxx ! msdkh265enc ! msdkh265dec ! glimagesink with changed frame size, e.g. from 1920x1080 to 1920x240

The root cause is a same dmabuf fd is used for frames with different size, which causes some unexpected result. This patch requires cached response is used for frames with same size only for DMABuf, so a dmabuf fd can't be used for frames with different size any more.

Merge request reports

Loading