https://bugs.kde.org/show_bug.cgi?id=517726
Bug ID: 517726
Summary: Memory Leak when watching/rewatching horizontal bar
composite transition.
Classification: Applications
Product: kdenlive
Version First 25.12.3
Reported In:
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: Monitors & Playback
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 190753
--> https://bugs.kde.org/attachment.cgi?id=190753&action=edit
Removed all of the "* = new object"s that I found and corrected -> to . where
appropriate. Added &s for references where functions took pointers before.
SUMMARY
I did test and verify it only happens when watching a horizontal bar composite
transition (or at least does not happen with dissolve).
STEPS TO REPRODUCE
1. Add two video tracks.
2. Add composite between them.
3. Use horizontal bar.
4. Play videos with project monitor.
You don't even need to actually change any keyframes or anything.
OBSERVED RESULT
Memory usage constantly increases until I run out of memory.
EXPECTED RESULT
kdenlive to not use 20+GB of memory.
SOFTWARE/OS VERSIONS
Linux: Fedora 46
kdenlive: kdenlive-25.12.1-x86_64 (app image version)
ADDITIONAL INFORMATION
https://www.youtube.com/watch?v=ZDGP-Zyiljk recording of me testing and
recreating the bug
I see a lot of "auto *<variable_name> = new ClassName();" in monitor.cpp.
Not a single one of those needs to be a pointer, but I'm not sure if those
specifically are causing this problem.
You could band-aid fix that by adding deletes, but the actual problem is using
new in C++ which should almost never be done.
I can't build kdenlive on my machine, but I will attach my edited monitor.cpp
if you care.
--
You are receiving this mail because:
You are watching all bug changes.
