Bug 380224 - Kdenlive process doesn't go away after closing
Summary: Kdenlive process doesn't go away after closing
Status: RESOLVED DUPLICATE of bug 401872
Alias: None
Product: kdenlive
Classification: Applications
Component: Setup & Installation (show other bugs)
Version: 18.08.2
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-26 12:51 UTC by de7983a4
Modified: 2019-01-04 13:52 UTC (History)
2 users (show)

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

Attachments
An example (12.01 KB, image/png)
2017-05-26 12:51 UTC, de7983a4 		Details
Kdenlive-kill (250 bytes, text/plain)
2018-08-06 16:37 UTC, emohr 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description de7983a4 2017-05-26 12:51:59 UTC 
Created attachment 105724 [details]
An example

I had task manager open and was running Kdenlive.
I saw that there was a kdenlive.exe process and a kioslave.exe process.
This is from the program of course, but whenever I close Kdenlive, the processes are still there, and when I open Kdenlive again the old processes are still there and Kdenlive creates new processes.

OS: Windows 10 Creators Update (1703)
FFmpeg 20170525-b946bd8 win64 shared
Breeze-icons is missing because it was not included with the Kdenlive zip for Windows (fix this please).
Processor: Intel Core i7 4790
Motherboard: MSI H97 PC Mate(MSI-7850)
RAM: 8 GB DDR3
GPU: NVIDIA GeForce GTX 750
Comment 1 Richard Godbehere 2017-11-05 21:47:28 UTC 
Also having these issues, processes not closing and missing Breeze-icons. Problem still exists as of version 17.08.1

Running Windows 10 Fall Creators Update (1709)
AMD Phenom X6 1055T
Asus M4A88TD-V EVO/USB3
4GB DDR3
AMD Radeon 6970
Comment 2 emohr 2018-08-06 16:37:19 UTC 
Created attachment 114335 [details]
Kdenlive-kill
Comment 3 Vincent PINON 2019-01-04 13:52:00 UTC 
*** This bug has been marked as a duplicate of bug 401872 ***