Created attachment 160337 [details] Just a screenshot of the job queue SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. try to render a video OBSERVED RESULT It gets stuck on waiting EXPECTED RESULT It renders SOFTWARE/OS VERSIONS Flatpak 1.15.4 Kdenlive 23.04.3 ADDITIONAL INFORMATION
I have this behaviour in the version 23.08.2, though may be it's a different bug. The problem is present in BOTH the AppImage and the Flatpak release. Additional info: 1. The problem is present only when using proxies. Codec used for proxies (H264 or MJPEG) does not matter. 2. Although rendering seems to be stuck in the preparation phase for a very long time the project is eventually rendered fine. 3. There are no useful messages displayed in the terminal during the wait. When using gdb there are only several "Thread [...] exited" messages and nothing else. 3. Rendering can be immediately aborted during the wait, the message "QProcess: Destroyed while process ("/app/bin/melt") is still running" is displayed in the terminal (with gdb). 4. The more proxified clips are in the project the longer is the wait. On my system (Ryzen 7 2700 Eight-Core) it is about 1min 30sec for 50 clips. 5. Number of clips used in the timeline has no matter, only the total number of clips with proxies in the project bin matters. For me everything points to a bug in MLT.
We fixed an MLT issue, which should solve this type rendering problem. Please try with the latest 24.08.1 AppImage from the download page.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Thank you! The problem does not appear anymore, and in fact it does not since a long time ago. Marking as resolved and fixed.