Fedora 24 KDE 5.26 QT 5.6.1 MLT 6.2.0 AMD 8 Core 24GB RAM Recently started having an issue with Kdenlive. As far as I can tell it's only involving raw footage on a particular hard drive (although that could be a red herring). I had top running the other day after dealing with this issue and trying to debug it. CPU usage that top said was due to Kdenlive went past 100% and then it locked up. I can't control-alt-F# to any other terminal. I can't activate num lock or caps lock. The mouse doesn't move. The screen doesn't update. The fan on the CPU remains full speed. I waited 10 minutes - it did not unlock itself. I don't know if this is relevant, but I have the following in the terminal when I run kdenlive: $ kdenlive QXcbConnection: XCB error: 8 (BadMatch), sequence: 14744, resource id: 136315231, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 14767, resource id: 136315231, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 26607, resource id: 136315231, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 26630, resource id: 136315231, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 28354, resource id: 136315231, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 28377, resource id: 136315231, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 28402, resource id: 136315231, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 28429, resource id: 136315231, major code: 130 (Unknown), minor code: 3 Reproducible: Always Steps to Reproduce: 1. Load up video 2. Scrub through video or sometimes while creating the audio preview 3. Entire system locks up Actual Results: Entire system locks up Expected Results: System not to lock up
Some extra comments I was thinking of: 1) Might not be the hard drive that has those clips, maybe it's because they're clips that came from a Canon Rebel T6s. I've been able to use it in the past without issue, but perhaps something in one of the dependencies for Kdenlive has changed. 2) Just experienced the lockup on Rendering twice - same file. 3) I'm using Nvidia proprietary drivers - latest RPMFusion RPMs 4) Info on one of the video files based on VLC: Video codec: H264 part 10 avc1 Frame rate: 29.9 1920x1080 resolution 5) I had to switch to the gstreamer backend instead of VLC backend in KDE and the video file doesn't play. But I think based on when I had top running that Kdenlive calls ffmpeg
I don't know what this tells you, but I ran the new alpha App Image you guys posted today and had the same issue - crash on a render. So I bumped up the version number. On the theory that it's maybe a corrupt kdenlive file or something like that - basically, I had a template already set up with the way I wanted things, but it was from the older version of kdenlive. Also, an asset had been deleted and I was using a placeholder asset. So maybe something's borked on there? So I'm going to try rendering one of the Canon Rebel T6s files from the same hard drive in a brand new kdenlive file and see what happens.
Created attachment 101759 [details] The file that keeps dead-locking the system On the off chance that you can discover something by seeing the kdenlive file, here it is.
One more thing before this gets too spammy (if it's not already there) - I was able to render a 47 second file from the Canon Rebel T6s without any effects on it - without a hard crash. So to recap: 1) Doesn't appear to simply be the video file 2) Even in the Kdenlive Alpha Appimage - with the same kdenlive file it hard crashes. Right now it seems to my mind (someone who's technical, but not when it comes to coding a non-linear video editor) that the most likely culprit seems to be the kdenlive file. I'm going to attempt to recreate it as best as I can (obviously, I won't be able to get the cut points exact) and see if that fixes the issue.
Created attachment 101761 [details] This file worked OK This file worked fine. Rendered OK - did not hang the comptuer. It's not exactly the same as I couldn't make it the same, I also simplified the opening by pre-rendering it, but I'm attaching the file in case looking at this one and the other helps you see what was causing the hang.
Worked on a new file today and it once again locked up the system. I'm going to try running melt on its own to see if that works. If you have any other suggestions, let me know.
Can't actually do that as Fedora's mlt package apparently doesn't have melt.
System lockups are a clear indication that your system is defective. This may be a driver issue, a hardware issue, or some corrupted system or library file. There is nothing we can do about it from our perspective. Nothing you've reported indicates that there's a problem with the Kdenlive code base. In order to keep our bug report level manageable please understand that we are closing this report; you can reopen it when you have clear evidence of a bug in Kdenlive's code base. Thank you very much for your understanding.