I’ve been using Kdenlive for a few months now, and the most crashes I’ve noticed are related to undo/redo or undo history panel.
If I go back a far in history, it crashes sometimes.
Further, sometimes it crashes when I do some action like:
Undo > Undo > Redo. (Using Ctrl Shift Z shortcuts).
I’m wondering why these happen and when can we expect a fix.
What platform are you on and what build are you using? I occasionally see undo/redo get confused, but it’s been a while since I’ve seen it cause a crash.
If you can create minimal examples of a crashing combination (preferably with just intrinsics like colour clips etc that don’t need you to include source video), that’s something that can be debugged and fixed.
Every different thing has its own undo handling though, so the number of possible permutations and interactions is Pretty Big, and it’s not “one problem that’s just waiting for a fix”.
Most of them should be reasonably easy to find and fix with a good test to reproduce the crash though.
I’d try next time to see if same action can be repeated again to reproduce them and then submit.
I’m on Windows 11 PC. i5 12400F, RTX 3050, 16GB RAM and SSD.
Version 24.12.0
I’ve also had this problem (on Linux) for a long time. I’ve gotten used to it and often save in between.
Even when changing a color in the text, Kdenlive likes to crash if I undo very often. But that’s not so bad, because the automatic recovery can save almost all steps.
You can really live with this error. Vegas Pro was even more unstable.
I agree it’s mostly not a showstopper, but we shouldn’t have to Just Live With It - and they mostly shouldn’t be too hard to fix iff people report reproducible cases of it happening (“it crashed when I used undo” we can’t debug - “it crashes every time I do the steps X, Y, Z in a minimal new project” we absolutely can).
In most cases it’s quite likely to be that some intermediate step in an undo chain did not push its reverse operation perfectly onto the stack, so later (or earlier…) undo steps then try to operate on a state that hasn’t been restored and things Go Badly when things that should be aren’t there.
I personally rarely see crashes from this in normal use, but probably because I rarely undo more than one step (or one kind of step), and I’m always careful to check if it actually correctly undid whatever I’m backing out of. (and I’ve probably subconsciously learned which to revert manually with my get the job done as a user hat on)
But the goal should be to (eventually) fix all of these, not accept them as “still better than the other guys!”. It won’t happen overnight - but it also won’t happen for a very long time if people don’t report the ways they find to reproduce them.
That is an issue, most crashes I notice are not reproducible. So that’s a genuine bug yet no hope for fix.
If it’s really crashing that “randomly” for you, I’d be checking your system or if you’re starving it for ram. This really isn’t the sort of code that has a whole lot of lost race type issues, it’s generally pretty deterministic.
But if you can get a crash dump and backtrace, that can help too.