I'm trying to use "shotcut", installed in a Fedora 41 virtual machine, to split
up some large mp4 files. It can read the files and play the videos just fine, so there is
apparently no decoder issue, but any time I try to do anything with the file the process
segfaults. Suspecting there might be a memory issue with these large files (7.5GB on the
largest, but same result on an 862MB file), I increased the VM's memory allocation to
32GB. No difference. There is no sign that the system is running out of memory.
Here is a typical sequence:
Create a new project, "Test1",
Drag an mp4 file from the "Recent" area into the Playlist,
Double-click on the Playlist snapshot to select it and start the video
playing,
After about 90 seconds, without doing enything else, the process segfaults.
Heck, I find that if I just drag the mp4 into the playlist and do nothing else
(not even playing the video), the process still segfaults after about 2
minutes, all of this with no appreciable CPU activity in the meantime.
Here's the tail of the generated shotcutlog.txt file:
[Info ] <MainWindow::open> "/Public/S862M.mp4"
[Debug ] <Playlist::InsertCommand::redo> row 0
[Info ] <MLT> [link swresample] 2(stereo) f32le 44100Hz -> 2(stereo) s16
48000Hz
[Info ] <MLT> [link swresample] 2(stereo) f32le 44100Hz -> 2(stereo) s16
48000Hz
[Info ] <MLT> [consumer sdl2_audio] Audio Opened: driver=pulseaudio
channels=2 frequency=48000
[Info ] <MLT> [link swresample] 2(stereo) f32le 44100Hz -> 2(stereo) s16
48000Hz
[Info ] <MLT> [link swresample] 2(stereo) f32le 44100Hz -> 2(stereo) s16
48000Hz
[Info ] <MLT> [link swresample] 2(stereo) f32le 44100Hz -> 2(stereo) s16
48000Hz
[Info ] <Util::isMemoryLow> available RAM = 31469388 KB
[Debug ] <autosaveTask> Function autosaveTask finished in 3 ms.
[Info ] <Util::isMemoryLow> available RAM = 31472564 KB
Nothing obvious in the journal:
May 17 22:14:00 fedora-vm.local audit[2788]: ANOM_ABEND auid=1000 uid=1000
gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=2>
May 17 22:14:00 fedora-vm.local kernel: show_signal_msg: 40 callbacks suppressed
May 17 22:14:00 fedora-vm.local kernel: Thread (pooled)[2893]: segfault at 358 ip
00007f04a0a81494 sp 00007f04864f2378 error 4 in libc.so.6[74494,7f04a0a0>
May 17 22:14:00 fedora-vm.local kernel: Code: da f9 ff 48 8d 0d 7c 74 14 00 ba c2
01 00 00 48 8d 35 80 ea 13 00 48 8d 3d 8e ea 13 00 e8 14 da f9 ff 0f 1f >
May 17 22:14:00 fedora-vm.local systemd-coredump[2894]: Process 2788 (shotcut)
of user 1000 terminated abnormally with signal 11/SEGV, processing...
May 17 22:14:00 fedora-vm.local systemd[1]: Created slice
system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump.
May 17 22:14:00 fedora-vm.local audit: BPF prog-id=71 op=LOAD
May 17 22:14:00 fedora-vm.local audit: BPF prog-id=72 op=LOAD
May 17 22:14:00 fedora-vm.local audit: BPF prog-id=73 op=LOAD
May 17 22:14:00 fedora-vm.local systemd[1]: Started
systemd-coredump@0-2894-0.service - Process Core Dump (PID 2894/UID 0).
May 17 22:14:00 fedora-vm.local audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-core>
May 17 22:14:00 fedora-vm.local abrt-dump-journal-core[983]: Failed to obtain
all required information from journald
May 17 22:14:01 fedora-vm.local systemd-coredump[2895]: [🡕] Process 2788
(shotcut) of user 1000 dumped core.
{Huge module list and stack trace deleted}
I don't know what is happening -- perhaps some timed auto-save that blows up??
(I don't see any setting to disable that.)
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
