On 20/09/17 17:10, Andy Furniss wrote: > Mark Thompson wrote: >> On 19/09/17 22:21, Andy Furniss wrote: > >>> That point being around 7k frames it will run out of something. >>> >>> [AVHWFramesContext @ 0x31ed880] Failed to create surface from DRM object: 2 >>> (resource allocation failed). >>> [Parsed_hwmap_0 @ 0x3114c40] Failed to map frame: -5. >>> >>> I see that memory is reducing before this although I still have spare - is >>> this the same issue you explained on users WRT leaking on decode? >> >> Yeah, I also run out of ... something ... at around 7200 frames. It's not >> fds or memory. I don't think it's the buffer problem (which, incidentally, >> should finally be fixable sensibly in libva2 soon), because that ended up >> manifesting as leaking memory. It's also not a problem for Intel (I've >> already been running that for a long time to test). Maybe some other sort >> of handle on the Mesa side? I'll investigate further tomorrow. > > Leo has fixed the leak.
Yep, checked with the updated Mesa postproc patches + libva2 fixes and it all looks good now. (And colours are even correct, yay! I still need to look into why the default comes out wrong with the postproc bits for that on Intel...) Thanks, - Mark _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
