Hello there, I've ran into some scenarios where a long running FFmpeg process configured to use NVDEC crashes with the error message: illegal memory access, something related to cuda.
I'm unable to consistently reproduce this issue with concurrent runs as I'm transcoding live channels (provided as mpegts udp streams). When I'm back on my desk I'll try to copy and paste the exact error message and the FFmpeg command used. Are there private options that can be passed to the NVDEC hwaccel for maximum stability? I've seen the use of -extra_hw_frames 2 being recommended on a related ticket which presented a segfault when handling encodes with B-frames and deinterlace filter in the same flow, but I'm unable to replicate such a workaround. Warm regards, Dennis. _______________________________________________ ffmpeg-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
