Bug 514086 - kdenlive startup problems with VST Plugins (crash, Memory Leak)
Summary: kdenlive startup problems with VST Plugins (crash, Memory Leak)
Status: REPORTED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (other bugs)
Version First Reported In: 25.12.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-02 20:09 UTC by blackcat00
Modified: 2026-01-05 10:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description blackcat00 2026-01-02 20:09:46 UTC
SUMMARY
I updated my Kdenlive on Windows 10 from version 24 to the current version 25.12. 
Unfortunately, Kdenlive does not start anymore. 
I've tried several versions, and it seems the problem originates somewhere around version 24.12.

STEPS TO REPRODUCE
I've discovered that there seems to be an issue with VST plugins, which are all located in a single folder on my hard drive. 
The collection is quite large. 
If I rename the folder, Kdenlive starts normally. 

OBSERVED RESULT
When the VST plugins are present, the following occurs:

Very long loading time after the splash screen. The window in the upper left corner flickers briefly every now and then. Kdenlive then loads up to 13GB into RAM and then freezes without a visible window or terminates its task.

I read this: https://bugs.kde.org/show_bug.cgi?id=498160 and saw something about a blacklist.
but i dont get any console output on windows terminal where i could see the plugin that could make problems. (Mixcraft 10 Pro Studio is also on my system aside of many other VST plugins)

Is this also available in the Windows version?

Wouldn't a whitelist be possible as well?


Is there any way I can find out exactly what's happening and perhaps modify the VST folder programmatically so that it doesn't try to initialize everything?



SOFTWARE/OS VERSIONS
Windows: 10 (22H2)
Comment 1 blackcat00 2026-01-05 10:41:34 UTC
Since Kdenlive only starts the plugin scan after the intro dialog, 
wouldn't it be possible to programmatically reset the VST path or set it to a user-defined path from the Kdenlive configuration?

Something like 

```
_setenv("VST_PATH", config_vst_path.c_str(), 1);
_setenv("VST3_PATH", config_vst3_path.c_str(), 1);

initializeMLT();
```