I noticed you commited an "fix memleaks" in git today. Having just recently installed Valgrind, I decided to let it run against kdenlive to see what it says. Of course it's painfully slow, and it shows a whole host of errors in mlt and kdenlive. I have compiled both with full debugging symbols, so it points right at the worst memory errors and unintialized variables, etc. I'll attach the logs here, and file a report for mlt as well. In both cases, I started kdenlive through Valgrind, with a 1080p profile, which uses 720p proxy clips. Then I loaded on 4k clip, waited for the proxy to be made. Then I started a new project, same parameters, no save. Loaded another 4k clip, and once the proxy was made dragged it down to the timeline. Then I clicked onthe timeline to position the "playhead" on the clip, and to activate the project montior. Then I exited the program. Attaching the logfiles now. Reproducible: Always
Created attachment 99663 [details] logfile captured from terminal, just a plain "valgrind kdenlive"
Created attachment 99664 [details] full valgrind log This is the full log of the command: valgrind -v --track-origins=yes --log-file=kdenlive.valgrind.2016-06-22.txt kdenlive Both mlt and kdenlive has been built with debugging on, and nothing stripped out.
Should be fixed with Kdenlive version 16.08
I will provide valgrinds upon request for any branch where we are cleaning it up.