Latest release branch from git 18.08 crashes when automatically adding a clip to the project after it has been stabilized with the clip job vidstab. If you want a back trace I would be happy to oblige. -Evert-
When running from the console, I get this error message when the crash occurs: ----------------snip---------------------- New Thread 0x7ffec47e8700 (LWP 6983)] [New Thread 0x7ffec4fe9700 (LWP 6984)] [New Thread 0x7ffec57ea700 (LWP 6985)] [New Thread 0x7ffec5feb700 (LWP 6986)] [New Thread 0x7fff31a52700 (LWP 6987)] [New Thread 0x7fff31251700 (LWP 6988)] [New Thread 0x7fff30a50700 (LWP 6989)] [New Thread 0x7ffef3fff700 (LWP 6990)] [New Thread 0x7ffe537fe700 (LWP 6991)] [IMGUTILS @ 0x7ffeb2ffc6f0] Picture size 1701277281x100 is invalid Cannot allocate memory. sws: initFilter failed [New Thread 0x7ffdb5ffa700 (LWP 6992)] Thread 1301 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffeb2ffd700 (LWP 6964)] 0x00007ffff506abb5 in __memmove_sse2_unaligned_erms () from /usr/lib/libc.so.6 (gdb)
What do you have for a strange Picture size: 1’701’277’281x100 1 Billion, 701 million, … length and just 100 pixel high.
To elaborate a bit more... I right-click on a clip in the project bin, select clip jobs, then stabilize. On the menu that pops up, I select automatically add to project. I can then see the clip is being analyzed with it's little progress indicator, but when the time comes to add the .mlt file to the project, the whole UI disappears with a segfault. So, two things are wrong. 1. an invalid .mlt file is being generated. 2. the UI segfaults, rather than give an error message. Now, I have tried this with latest packages from Arch Linux for both kdenlive and mlt, and the segfault still occurs. I have now (2018-09-18) compiled mlt from git, the latest master branch, and kdenlive from latest application 18.08 branch, and now it looks like the .mlt files being generated at least don't segfault the UI anymore, but they still have a lot of issues, outside the scope of this bug. The git logs of both applications do not have anything obvious about .mlt file generation in them recently, which is weird. However, bottom line is that the UI should not segfault just because an input file is invalid, and an error message indicating that the stabilization failed and maybe the output from console for that bit would be a nice touch. It would certainly help for more clear bug reports.
Do you use the VideoStab with right click on the clip (Videostab2) which is outdated or do you use VidStab under the effects? For VidStab under effect here some explanation of the values: https://www.mltframework.org/plugins/FilterVidstab/
*** Bug 382854 has been marked as a duplicate of this bug. ***
*** Bug 382333 has been marked as a duplicate of this bug. ***
*** Bug 383201 has been marked as a duplicate of this bug. ***
I change the version to refactoring timeline as this version is affected as well.
emohr, please read comment #3. I use Vidstab2, from the clip jobs in the context menu from the project bin. TLDR #1; The UI should not crash from normal user input. TLDR #2; That job generates invalid .mlt file Kind regards, Evert
Hi Evert. Yes I read comment 3 but I see the link is missing that Vidstab2 is deprecated. More details here: hhttps://www.mltframework.org/plugins/FilterVideostab2/ and here https://sourceforge.net/p/mlt/bugs/185/ So I understand we should not use Videostab2 anymore.
Hi there, emohr. To re-iterate from comment #3. 1. an invalid .mlt file is being generated. 2. UI crashes with invalid input. If changing the backend vid.stab in project manager clip jobs will fix #1, then maybe it's something that needs to be done. That still leaves #2... The error handling on input files of the UI needs work. Personally, I use Blender 3D to stabilize and render these days. Kind regards, -Evert-
Stabilizations on the clip jobs are now automatically added, and does not crash the UI