Bug 386292 - Crash using Vid. Stab Deshake effect
Summary: Crash using Vid. Stab Deshake effect
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: Effects & Transitions (show other bugs)
Version: 17.08.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-28 20:09 UTC by tszym
Modified: 2019-01-27 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: timeline_corruption+


Attachments
backtrace (14.65 KB, text/plain)
2017-11-12 16:58 UTC, tszym
Details
New crash information added by DrKonqi (14.82 KB, text/plain)
2017-12-21 00:55 UTC, James Vaughan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tszym 2017-10-28 20:09:59 UTC
Hello,

I wanted to test what the Vid. Stab Deshake effect does and here is what happened:

- I dragged a video clip on the timeline
- I dragged the Vid. Stab Deshake effect from the Effects list to the clip on the timeline
- Kdenlive crashed: segmentation fault (core dumped)  kdenlive

I reproduced the same event every time I tried to apply this effect on a clip.
Comment 1 tszym 2017-11-12 16:58:40 UTC
Created attachment 108808 [details]
backtrace

Here is the backtrace I get following the bug report manual.
Comment 2 Christoph Feck 2017-11-29 17:56:40 UTC
It crashes in libvidstab.so when parsing motions file, not sure if that is created by MLT.

I suggest to report this issue to MLT developers via https://github.com/mltframework/mlt/issues

Relevant part of the backtrace:

#0  0x00007ffff03c6cdf in __GI__IO_vfscanf () at /usr/lib/libc.so.6
#1  0x00007ffff03d60c6 in __isoc99_fscanf () at /usr/lib/libc.so.6
#2  0x00007fffc40babbd in restoreLocalmotion () at /usr/lib/libvidstab.so.1.1
#3  0x00007fffc40bad96 in vsRestoreLocalmotions () at /usr/lib/libvidstab.so.1.1
#4  0x00007fffc40bb128 in vsReadFromFile () at /usr/lib/libvidstab.so.1.1
#5  0x00007fffc40bb1cb in vsReadLocalMotionsFile () at /usr/lib/libvidstab.so.1.1
#6  0x00007fffbed9e7d7 in  () at /usr/lib/mlt/libmltvidstab.so
#7  0x00007ffff71d5b52 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#8  0x00007ffff71ec70b in  () at /usr/lib/libmlt.so.6
#9  0x00007ffff71d5b52 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#10 0x00007ffff6fbb27e in Mlt::Frame::get_image(mlt_image_format&, int&, int&, int) () at /usr/lib/libmlt++.so.3
Comment 3 tszym 2017-12-03 11:18:01 UTC
I thought libvidstab.so to be working as expected, because I think I am using it through ffmpeg and it works well.

$ ffmpeg -i source.MP4 -vf vidstabdetect=shakiness=8:accuracy=15:result="transforms.trf" -f null -
$ ffmpeg-i source.MP4 -vf vidstabtransform=smoothing=60:input="transforms.trf",unsharp=5:5:0.8:3:3:0.4 out_stabilized.mp4

This works without any crash. I am not 100% sure this is using libvidstab.so but it looks like it does to me. With these informations, do you still think this should be handled by MLT?

Thanks
Comment 4 James Vaughan 2017-12-21 00:55:59 UTC
Created attachment 109466 [details]
New crash information added by DrKonqi

kdenlive (17.12.0) using Qt 5.10.0

- What I was doing when the application crashed:

Dragged a video on to the timeline.
Dragged the deshake effect on to the clip on the timeline.
Kdenlive crashed.

-- Backtrace (Reduced):
#5  0x00007f5c7051f420 in __lll_unlock_elision () at /usr/lib/libpthread.so.0
#6  0x00005556faf7effb in  ()
#7  0x00005556fb014bfe in  ()
#8  0x00005556fafad787 in  ()
#9  0x00007f5c7525169e in QUndoCommand::redo() () at /usr/lib/libQt5Widgets.so.5
Comment 5 emohr 2018-12-28 15:47:15 UTC
"Vid.Stab Deshake" and "Deshake":
Tested with Kdenlive_Nightly_Appimage 27.Dec 18 -> no crash.

Please try with the current Kdenlive_Nightly_Appimage
https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/

Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage
Comment 6 Bug Janitor Service 2019-01-12 04:33:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2019-01-27 04:33:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!