Hi everyone,
I wanted to open a discussion to see if anyone else is running into a couple of very specific edge-case crashes in recent builds. For context, I’m running Kdenlive on Windows 11 with 32GB of RAM., I9 Processor, Nvidia GeForce RTX 4060 GPU. Outside of these two scenarios, the software has actually been incredibly stable for me during active editing, but these two triggers consistently cause the interface to go completely unresponsive. Only using the latest release version of Kdenlive, no beta
I plan on submitting formal bug reports, but I wanted to check in with the community first to see if these are known quirks or if others can replicate them.
- The Mixed Framerate / Profile Switch Prompt
The first crash happens right at the start of a project. When I drop a mix of clips into the bin, Kdenlive does its job and detects that the first clip doesn't match the current profile, prompting me to switch the default frame size and rate.
If I am mixing 29.97 fps and 30 fps footage without pre-transcoding, interacting with this automatic profile-switch prompt frequently causes a hard freeze. I know I can disable this prompt entirely in the settings, but when working with mixed media, it's a helpful safety net, when it doesn't crash the UI.
- UI Navigation During Proxy Generation
The second issue is a classic thread/UI lockup. If I import a large batch of footage and Kdenlive starts generating proxies, the UI becomes a ticking time bomb. Specifically, if I navigate through subfolders within the Kdenlive Project Bin while proxies are actively generating, the interface completely freezes.
My current workaround is literally "don't touch the interface." I've learned to just go grab a coffee while the proxies bake. Once they are done, I can click around safely again. It feels like a race condition or a UI thread blocking issue when the Project Bin is being updated simultaneously by the proxy worker and user navigation.
Is anyone else seeing this behaviour on Windows?
I'd love to know if this is a known bottleneck with the Windows build's thread management or if there are specific environment tweaks I can test before I gather the logs for the bug tracker.
Thanks