kdenlive crashed with SIGSEGV in mlt_filter_process()

[Richard Joreid]

full of buggs

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: kdenlive 4:15.12.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-18.34-lowlatency 4.4.6
Uname: Linux 4.4.0-18-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Fri Apr 8 09:55:11 2016
Disassembly: => 0x7f467dfce230: Cannot access memory at address 0x7f467dfce230
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/kdenlive
InstallationDate: Installed on 2016-03-25 (13 days ago)
InstallationMedia: It
ProcCmdline: kdenlive
SegvAnalysis:
 Segfault happened at: 0x7f467dfce230: Cannot access memory at address 0x7f467dfce230
 PC (0x7f467dfce230) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: kdenlive
StacktraceTop:
 ?? ()
 mlt_filter_process () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
 mlt_service_apply_filters () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
 mlt_service_get_frame () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
Title: kdenlive crashed with SIGSEGV in mlt_filter_process()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip fax floppy libvirtd lpadmin netdev plugdev root sambashare scanner sudo tape video

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 mlt_filter_process () from /tmp/apport_sandbox_Hzu7Ma/usr/lib/x86_64-linux-gnu/libmlt.so.6
 mlt_service_apply_filters () from /tmp/apport_sandbox_Hzu7Ma/usr/lib/x86_64-linux-gnu/libmlt.so.6
 mlt_service_get_frame () from /tmp/apport_sandbox_Hzu7Ma/usr/lib/x86_64-linux-gnu/libmlt.so.6
 producer_get_frame () from /tmp/apport_sandbox_Hzu7Ma/usr/lib/x86_64-linux-gnu/libmlt.so.6

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.