Bug 419986 - Crash on exit (File->Exit results in SIGSEGV)
Summary: Crash on exit (File->Exit results in SIGSEGV)
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (other bugs)
Version First Reported In: 19.12.3
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-12 10:44 UTC by Stefan Naumann
Modified: 2020-04-12 14:29 UTC (History)
1 user (show)

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


Attachments
Backtrace from a bigger project (73.36 KB, text/plain)
2020-04-12 10:44 UTC, Stefan Naumann
Details
Backtrace from an empty project (14.71 KB, text/plain)
2020-04-12 10:45 UTC, Stefan Naumann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Naumann 2020-04-12 10:44:42 UTC
Created attachment 127464 [details]
Backtrace from a bigger project

SUMMARY
Opening kdenlive and hitting File->Exit results in a SIGSEGV. I tried it with a finished project, as well with an empty one and it occured both times, due to a Nullpointer-jump.

STEPS TO REPRODUCE
1. Open KDEnlive
2. Close it with File->Exit or by closing the Window

OBSERVED RESULT
Crashing, GDB said KDEnlive received SIGSEGV

EXPECTED RESULT
Normally closing, maybe call exit(0)

SOFTWARE/OS VERSIONS
Linux: 5.6.3-arch1-1
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
Running in i3 window manager
Comment 1 Stefan Naumann 2020-04-12 10:45:20 UTC
Created attachment 127465 [details]
Backtrace from an empty project
Comment 2 emohr 2020-04-12 12:52:48 UTC
Thank you for reporting. I think we have fixed this issue. 

Please try with the current Kdenlive_Nightly_Appimage
https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/
Comment 3 Stefan Naumann 2020-04-12 14:29:17 UTC
I've just build a nightly myself, and yes, it's fixed there.