[FFmpeg-trac] #10777(undetermined:new): Segfault when using hardware vaapi encoding
FFmpeg
trac at avcodec.org
Thu Jan 4 14:01:53 EET 2024
#10777: Segfault when using hardware vaapi encoding
-------------------------------------+-------------------------------------
Reporter: Patrick M | Owner: (none)
Type: defect | Status: new
Priority: normal | Component:
| undetermined
Version: unspecified | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by Charlie Turner):
I bisected this issue to
{{{
commit 8c7934f73ab6c568acaa47c821a6833f9145fdbb
Author: Niklas Haas <git at haasn.dev>
Date: Sun Dec 31 13:35:03 2023 -0800
avfilter: add negotiation API for color space/range
Motivated by YUVJ removal. This change will allow full negotiation
between color ranges and matrices as needed. By default, all ranges
and
matrices are marked as supported.
Because grayscale formats are currently handled very inconsistently
(and
in particular, assumed as forced full-range by swscale), we exclude
them
from negotiation altogether for the time being, to get this API
merged.
After filter negotiation is available, we can relax the
grayscale-is-forced-jpeg restriction again, when it will be more
feasible to do so without breaking a million test cases.
Note that this commit updates one FATE test as a consequence of the
sanity fallback for non-YUV formats. In particular, the test case now
writes rgb24(pc, gbr/unspecified/unspecified) to the matroska file,
instead of rgb24(unspecified/unspecified/unspecified) as before.
}}}
It would be nice to have some automated CI for the h/w acceleration. We'll
hopefully have something like this at my company soon. Not sure if FATE is
suitable for tests requiring a GPU.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/10777#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list