Bug 373474 - git master - crashed while clicking on a position in Timeline. [backtrace log included]
Summary: git master - crashed while clicking on a position in Timeline. [backtrace log...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (other bugs)
Version First Reported In: git-master
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-09 17:59 UTC by Unknown
Modified: 2019-01-01 19:36 UTC (History)
3 users (show)

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

Attachments
backtrace log (13.13 KB, text/plain)
2016-12-09 17:59 UTC, Unknown 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2016-12-09 17:59:03 UTC 
Created attachment 102710 [details]
backtrace log

I'd originally been using gdb to record for a different bug, but this came up in the process. I think I noticed Kdenlive froze and Terminal reported crash after I had left-clicked a location in the timeline.

Crash bug discovered while using Kdenlive 17.03.70 git master ppa on Antergos (Arch) Linux x64, GNOME 3.22.2 desktop environment, Xorg 1.18, kernel 4.8.12-13 ARCH.
Comment 1 farid 2016-12-10 00:31:39 UTC 
Please provide instructions on how to reproduce it.
Comment 2 Unknown 2016-12-11 18:59:43 UTC 
Sorry Farid, it came up haphazardly -- I wasn't able to remember the exact steps. :/ I was hoping that the backtrace log would be able to fill in the gaps in my info'. If there's nothing helpful in the logs, feel free to close the bug and I'll re-open a new one if I can repeat it.
Comment 3 emohr 2019-01-01 19:36:24 UTC 
I don't see something crash specific in the log.

If you like you can test with the current Kdenlive_Nightly_Appimage: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/

We closed this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.