Bug 388416 - vidstab: Crash if two clips are stabilized at the same time
Summary: vidstab: Crash if two clips are stabilized at the same time
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: Video Effects & Transitions (other bugs)
Version First Reported In: 17.12.0
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-01 08:14 UTC by mau
Modified: 2019-01-27 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
fritzibaby: timeline_corruption+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mau 2018-01-01 08:14:50 UTC
If I create the stabilized version of two different clips at the same time, kdenlive crashes when the faster stabilization finishes and the clip gets added to the project bin, while the slower stabilization is still running.
Comment 1 mau 2018-01-01 08:18:00 UTC
Additional info: proxy clips are enabled, maybe the crash happens when the first proxy clip creation starts.
Comment 2 mau 2018-01-01 08:21:16 UTC
Now a crash also occurred only creating one vidstab clip - but normally kdenlive didn't crash then, while creating several vidstab clips at the same time let it crash every time.
Comment 3 mau 2018-01-01 08:45:05 UTC
Several clips and crashes later I think I can state the following:
Crashes happen after the mlt file has been created and when the new clip gets added to the project bin; I can see it being added just before kdenlive crashes.

If I deactivate "Add clip to project" in the vidstab dialog, kdenlive doesn't crash.

Adding the vidstab-clips manually to the project bin never yielded a crash.
Comment 4 emohr 2018-12-28 16:53:31 UTC
VideoStab with right click on the clip (Videostab2) is deprecated. Use VidStab under the effects. Do you have the same problem?
Comment 5 Bug Janitor Service 2019-01-12 04:33:12 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 6 Bug Janitor Service 2019-01-27 04:33:15 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!