Bug 498756 - Kdenlive Freezing when Stabilizing a Clip in Fedora 41
Summary: Kdenlive Freezing when Stabilizing a Clip in Fedora 41
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Video Effects & Transitions (show other bugs)
Version: 24.12.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2025-01-16 17:30 UTC by otterslide
Modified: 2025-03-05 15:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
crash log (100.88 KB, text/plain)
2025-01-16 17:30 UTC, otterslide
Details

Note You need to log in before you can comment on or make changes to this bug.
Description otterslide 2025-01-16 17:30:27 UTC
Created attachment 177424 [details]
crash log

SUMMARY
Stabilizing a clip in Kdenlive on Fedora results in Kdenlive freezing and sometimes crashing.

STEPS TO REPRODUCE
1. Go to Clip Jobs and Stabilize on a longer 4K Clip

OBSERVED RESULT
Kdenlive often freezes, although sometimes succeeds.  Rarely it crashes.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux fedora 6.12.9-200.fc41.x86_64 with XFCE
KDE Plasma Version: NA
KDE Frameworks Version:  NA
Qt Version: 6.8.1

ADDITIONAL INFORMATION
I attached the crash report, although I'm unable to get it to crash again while running with gdb.  It's mostly freezing and not crashing.  I have tried a few older versions of qt6 Kdenlive, they all had the same issue.  This problem is not present on Ubuntu 23.10 on the same machine. Two separate Fedora 41 installs were tested.  "dnf install kdenlive" was tried, as well as AppImage with the same result.
Comment 1 emohr 2025-01-16 19:10:15 UTC
Thank you for reporting. That could be a mem-leak or you run out of memory.

Check the memory consumption and the CPU usage while stabilizing a 4K clip.
Comment 2 otterslide 2025-01-16 20:48:17 UTC
(In reply to emohr from comment #1)
> Thank you for reporting. That could be a mem-leak or you run out of memory.
> 
> Check the memory consumption and the CPU usage while stabilizing a 4K clip.

I did monitor it. It is not running out of ram. I have the zram set to a 3X system ram which is 16GB, so there's lots of swap and it's not being used at all when the problem happens.
There is something strange going on with RAM usage though, after using Kdenlive for a longer time on a big project, the RAM and swap keep filling up more and more while previewing the timeline. I have to restart Kdenlive to free it.  
I didn't have this problem on Ubuntu, but I have no idea why memory management would be different on Fedora.
While stabilizing, Kdenlive is at 2-10% CPU normally, but when the problem happens it jumps to 100% CPU and freezes like that until I terminate it.
Any ideas what I could try? I installed irqbalance and tried some kernels parameters but there's no improvement.  It's not very usable like this, so I'll have to switch back to Ubuntu if I don't find a fix.  
Thanks!
Comment 3 emohr 2025-02-18 09:39:33 UTC
Please try with the latest AppImage version 24.12.2 to see if the issue still exists. https://kdenlive.org/en/download/
Comment 4 Bug Janitor Service 2025-03-05 03:47:22 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 5 otterslide 2025-03-05 06:17:32 UTC
(In reply to emohr from comment #3)
> Please try with the latest AppImage version 24.12.2 to see if the issue
> still exists. https://kdenlive.org/en/download/

Tried 5 stabilize jobs, and all were successful.  Looks like it's fixed.
Comment 6 emohr 2025-03-05 15:55:51 UTC
Thank you for your feedback. Glad to here it works.

I close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.