Justin Ruggles <[email protected]> added the comment: confirmed that the behavior is the same with current libav git. unless this is a regression, it is just a normal bug, not critical.
---------- priority: critical -> normal status: new -> open substatus: new -> reproduced ______________________________________________ Libav issue tracker <[email protected]> <https://roundup.libav.org/issue2616> ______________________________________________
