[Bug]: Hard crash on Windows

[drzett]

Describe the bug

Such a nice plugin, thanks.

Sadly both, the CLAP and vst3 crash my host (full CTD, not even an error screen) when dialing in the effect (twisting knobs - "fast" maybe) while looping a section of the the project. Not instantly, but pretty fast and reproduceable. Didn't check other DAWs for now but I though, I'll make a short post about it.

I might do some more tests and update the issue as soon as I find time. I had it crashing 3 times now and opened this issue.

Keep it up and thanks again, I'd like to use this for sure.

How to reproduce

1. Open a medium sized project (I just didn't check on an empty project) in FL Studio (2025 beta 6 in my case)
2. Insert the plugin on a mixer track (vst3 or CLAP)
3. Loop a section of the project
4. Turn the knobs of the plugin (fast turning seems to crash easier than slow)
5. Host Crash to desktop for me (no error logs, no error screen)

Expected behavior

1. no crash

Screenshots / Videos

No response

Was this an official release or a self-compiled build?

Official release

Plugin version

1.1.0

Operating system

Windows

OS version

Win 11 Pro

CPU architecture

x86_64 (Intel/AMD 64-bit)

Plugin format

CLAP

DAW / Host application

FL Studio 2025 beta 6

Crash logs / stacktrace (optional)

Code of Conduct

• I agree to follow the Code of Conduct

[Lunix-420]

Hey, thanks a lot for the report and kind words!

Just letting you know I saw this and I’m currently trying to reproduce the crash. Been turning knobs as fast as I can while looping some FL demo project for like half an hour. So far, no success in reproducing the crash.

Did you adjust anything in the settings menu? (The one that opens when you click the cogwheel button, not the plugin parameters)

Also, do you have any idea if it happens on any project with any loop length, or do I need to do something specific, like put plugin ABC before it in the chain?

[drzett]

Hi, and thanks again for getting back to me so quickly.

I felt a bit bad at first for not narrowing down the issue more thoroughly before posting, but I’ve done a bit more testing now and can hopefully provide some useful input.

It turns out the crash doesn’t happen when the plugin is placed on a mixer track without any plugin latency on the instrument. In my case, that means: as long as the kick synth I’m using doesn’t introduce any latency, everything runs fine.

However, once latency is introduced – for example, when I enable Medium Look-Ahead in Kick 3’s internal limiter (which adds 2.5 ms of latency@48kHz) – the DAW is crashing shortly after I interact with the Disflux GUI. It seems to be consistently reproducible in that setup.

Of course, I can’t say for sure that your plugin is to blame, but I can say that with the same setup and different plugins, the issue doesn't occur.

I didn’t had time to dig in deeper last night. Hope this gives you something to work with. Github somehow won't let me upload my 14MB video with this comment... :-/

[Lunix-420]

Hey, appreciate you taking the time to dig into it more!

It turns out the crash doesn’t happen when the plugin is placed on a mixer track without any plugin latency on the instrument. In my case, that means: as long as the kick synth I’m using doesn’t introduce any latency, everything runs fine.

However, once latency is introduced – for example, when I enable Medium Look-Ahead in Kick 3’s internal limiter (which adds 2.5 ms of latency@48kHz) – the DAW is crashing shortly after I interact with the Disflux GUI. It seems to be consistently reproducible in that setup.

That's super helpful insight. Latency related stuff definitely narrows it down and gives me a solid lead to investigate. I’ll try to reproduce it with that setup as soon as I can.

Thanks again, really means a lot that you're interested in using the plugin and helping to improve it!

[Lunix-420]

We finally managed to reproduce the issue. Weirdly, it doesn’t happen on every machine, for example, on mine it just won’t crash no matter what I try.

Luckily, I found someone who experiences the crash consistently across all DAWs and can provide a stack trace. I’ll dive into fixing it ASAP.

[Lunix-420]

From my testing, this issue should be fixed now. The commit addressing it was pushed a while back, but the update is currently held up because of a bug in the Apple Developer app. It’s preventing us from renewing our developer license. That’s a problem since releasing a Windows only update isn’t really an option.

Sorry it took this long. It was a nightmare to even find a system where the issue occurred. On top of that, debugging was basically impossible as it wasn’t Disflux crashing, but an NVIDIA driver thread, so there were no useful logs or traces to work with. And to top it off, work and university completely ate up my time the past few weeks/months.

If anyone happens to read this and has a moment, I’d really appreciate it if you could try out the changes using this installer and let me know if it still crashes for you, or if it’s finally fixed on your end:

artifacts-windows.zip

Unless someone lets me know this didn’t fix it, I’ll push a new version as soon as Apple gets their act together and responds to my support request, been waiting two weeks now.

[sydonia86]

With those changes my crashes have stopped

[Lunix-420]

With those changes my crashes have stopped

That’s awesome to hear! Really appreciate you testing it. Sadly I still can’t push a proper release yet since Apple hasn’t got their shit together and managed to renew my developer account… still stuck waiting on them.

[Lunix-420]

The issue with apple is resolved, the update is coming this weekend.