Vincent Pinon

if you define USE_MLT_POOL=0 when compiling framework, you can use standard memory inspection tools

Maybe you could try prefixing melt command with "catchsegv" utility to get a stack trace and help debugging which service, which function fails. You must have debug symbols to provide...

I'd try first to add "-DCMAKE_BUILD_TYPE=RelWithDebSymbols" to [mlt options](https://github.com/mltframework/mlt-scripts/blob/master/build/build-melt.sh#L514) Another possibility would be to add "-g1" to [CFLAGS and CXXFLAGS](https://github.com/mltframework/mlt-scripts/blob/master/build/build-melt.sh#L86), but all libs would then become heavier...

Sorry I haven't spent any time on this. It's still on my todo list...

1 year later, still open. Since then, Kdenlive format has evolved and it is not the only issue :(

I'm just realizing these model evolution might be achieved by a new verilog-a implementation of basic devices, but then would it have an impact on performance? How to tell XDM...

Sorry, I'm not much involved in MLT & Kdenlive development for some time. Unfortunately `catchsegv` doesn't seem that reliable to catch segfault... I have read recently that it's in the...

Hello, This issue is causing me problems to package RTTR for debian sid and KDE Craft (GCC 8.1). Alternately, I simply [disabled Werror](https://cgit.kde.org/craft-blueprints-kde.git/tree/libs/rttr/FixGcc8Build.patch), which maybe is not very future-proof for...