| Summary: | Crashes just after a composition removal | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | lucky7tube |
| Component: | Video Effects & Transitions | Assignee: | Vincent PINON <vpinon> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | cgiraud, fritzibaby, julius.kuenzel, m8oxu4nv3 |
| Priority: | NOR | Flags: | fritzibaby:
Brainstorm+
|
| Version First Reported In: | 20.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | https://invent.kde.org/multimedia/kdenlive/commit/ad7cbbb994df4669ce464803eb5931c38ab2a940 | Version Fixed/Implemented In: | 21.08.1 |
| Sentry Crash Report: | |||
| Attachments: |
Crashes when remove a composition
ko_KR locale uses a point as decimal symbol, not a comma gdb log while kdenlive crashed |
||
This looks like the comma/point issue. Please change in the setting from comma to point or the other way around. See here: https://invent.kde.org/kde/kdenlive/issues/78#note_3980 BTW: such screengrab are always very helpful. Created attachment 120723 [details] ko_KR locale uses a point as decimal symbol, not a comma (In reply to emohr from comment #1) > This looks like the comma/point issue. Please change in the setting from > comma to point or the other way around. See here: > https://invent.kde.org/kde/kdenlive/issues/78#note_3980 > > BTW: such screengrab are always very helpful. Thank you for replying. But I don't understand because it works just fine with v19.04.1. Moreover, my locale is ko_KR, which uses a point as decimal symbol, not a comma. Deep consideration about latest changes will be appreciated. I'm having the exact same issue, either when I try to hit the delete button or when I right click on the transition/composition Could you make a test and switching the other way around from point to comma or vis versa to test if the crash is still there. https://invent.kde.org/kde/kdenlive/issues/78#note_3980 (In reply to emohr from comment #4) > Could you make a test and switching the other way around from point to comma > or vis versa to test if the crash is still there. > https://invent.kde.org/kde/kdenlive/issues/78#note_3980 I made the switch (from period to comma) and it still crashed (exactly like the video in attachment). Created attachment 130565 [details]
gdb log while kdenlive crashed
Crash always reproducible on my Ubuntu Studio 20.04 64bits and kdenlive 20.04.1: . create a new empty project . move 1 composition (Addition) to the empty time line . select spacer tool . select composition in time line and press "Del" key on keyboard to delete composition --> crash Same on linux with version 20.12.2 (updated above). It is not only happening with transitions, with the clips too if you use the spacer tool Additional information: ASSERT: "isItem(itemId)" in file kdenlive/src/timeline2/model/timelinemodel.cpp, line 263 Git commit ad7cbbb994df4669ce464803eb5931c38ab2a940 by Jean-Baptiste Mardelle. Committed on 05/08/2021 at 16:07. Pushed by mardelle into branch 'release/21.08'. Don't allow deleting items when a spacer move operation is running. M +1 -1 src/timeline2/view/qml/timeline.qml M +5 -0 src/timeline2/view/timelinecontroller.cpp https://invent.kde.org/multimedia/kdenlive/commit/ad7cbbb994df4669ce464803eb5931c38ab2a940 Seems solved with kdenlive-21.08.0a-x86_64.appimage Thanks! |
Created attachment 120681 [details] Crashes when remove a composition SUMMARY Kdenlive just crashes when removing a transition of a clip on the timeline. STEPS TO REPRODUCE 1. Import a video clip in the project bin 2. Place the clip on the timeline 3. (optional) Split the clip into several pieces, and overlap the pieces 4. Add a composition to some (overlapped or not) piece of the clip 5. Remove the composition previously added OBSERVED RESULT Kdenlive crashes immediately EXPECTED RESULT Intended composition gets removed and I should be able to keep editing SOFTWARE/OS VERSIONS Windows: 7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This bug is fresh with v19.04.2, never seen before.