Bug 2245732

Summary: [abrt] ffmpeg-free: fifo_peek_common(): ffmpeg killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Andrew <andrew.baker>
Component: ffmpegAssignee: Andreas Schneider <asn>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: andrew.baker, asn, dominik, multimedia-sig, ngompa13, philip.wyett
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e064f2f1b8def1e1f5730cace20aa574adbfa86
Whiteboard: abrt_hash:a60ae04c99c89ac66f45b6889aae9112cbb06c54;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-23 19:43:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: dso_list
none
File: backtrace none

Description Andrew 2023-10-23 19:21:18 UTC
Description of problem:
Launched Kdenlive, ffmpeg crashed during splash screen

Version-Release number of selected component:
ffmpeg-free-6.0-4.fc38

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         ffmpeg killed by SIGSEGV
journald_cursor: s=79a4bfb312164cbdaf0876c28d64e618;i=b889;b=d7cad8f2cd5e4292970e64ac6cd3aafb;m=2a0abd75e;t=60866fdd35bb3;x=c83360c4d3d07005
executable:     /usr/bin/ffmpeg
cmdline:        /usr/bin/ffmpeg -hide_banner -f lavfi -i color=s=640x360 -frames 1 -an -c:v h264_nvenc -f rawvideo pipe:
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.kde.kdenlive-34751.scope
rootdir:        /
uid:            1000
kernel:         6.5.7-200.fc38.x86_64
package:        ffmpeg-free-6.0-4.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: fifo_peek_common
comment:        Launched Kdenlive, ffmpeg crashed during splash screen

Truncated backtrace:
Thread no. 1 (12 frames)
 #0 fifo_peek_common at libavutil/fifo.c:203
 #1 av_fifo_read at libavutil/fifo.c:242
 #2 reorder_queue_flush at libavcodec/nvenc.c:181
 #3 ff_nvenc_encode_close at libavcodec/nvenc.c:1856
 #4 avcodec_close at libavcodec/avcodec.c:448
 #5 avcodec_open2 at libavcodec/avcodec.c:365
 #6 init_output_stream at fftools/ffmpeg.c:3233
 #7 init_output_stream_wrapper at fftools/ffmpeg.c:739
 #8 do_video_out at fftools/ffmpeg.c:1265
 #9 reap_filters at fftools/ffmpeg.c:1426
 #10 transcode_step at fftools/ffmpeg.c:4002
 #11 transcode at fftools/ffmpeg.c:4039

Comment 1 Andrew 2023-10-23 19:21:21 UTC
Created attachment 1995228 [details]
File: proc_pid_status

Comment 2 Andrew 2023-10-23 19:21:23 UTC
Created attachment 1995229 [details]
File: maps

Comment 3 Andrew 2023-10-23 19:21:24 UTC
Created attachment 1995230 [details]
File: limits

Comment 4 Andrew 2023-10-23 19:21:25 UTC
Created attachment 1995231 [details]
File: environ

Comment 5 Andrew 2023-10-23 19:21:27 UTC
Created attachment 1995232 [details]
File: open_fds

Comment 6 Andrew 2023-10-23 19:21:28 UTC
Created attachment 1995233 [details]
File: mountinfo

Comment 7 Andrew 2023-10-23 19:21:30 UTC
Created attachment 1995234 [details]
File: os_info

Comment 8 Andrew 2023-10-23 19:21:31 UTC
Created attachment 1995235 [details]
File: cpuinfo

Comment 9 Andrew 2023-10-23 19:21:33 UTC
Created attachment 1995236 [details]
File: core_backtrace

Comment 10 Andrew 2023-10-23 19:21:35 UTC
Created attachment 1995237 [details]
File: exploitable

Comment 11 Andrew 2023-10-23 19:21:36 UTC
Created attachment 1995238 [details]
File: dso_list

Comment 12 Andrew 2023-10-23 19:21:38 UTC
Created attachment 1995239 [details]
File: backtrace

Comment 13 Andrew 2023-10-23 19:43:06 UTC
This issue appears to be related to https://bugzilla.redhat.com/show_bug.cgi?id=2244239

*** This bug has been marked as a duplicate of bug 2244239 ***