Sounds like you’re experiencing the same exact issue I’ve described and not the one linked by Martin. It’s crazy that a company like Steinberg with a team of programmers allows for critical bugs like this to happen, while Cockos who make Reaper consist of two dudes who write the code and have 20000000x less issues with their software, while selling Reaper at a fraction of Cubase Pro price, lmao.
I would like to reiterate that Steinberg should be paying extra attention to proper sandboxing of VST3 plugins such that they are physically (logically) unable to take down their host by any means.
It’s too much of a risk to allow thousands of developers to do things that should be “illegal”, things that would cause the DAW to be destabilized. Cubase needs to be able to detect when a plugin its hosting is doing something wrong, alert the user, and if telemetry is enabled, instantly send a report with all the details back to the mothership at Steinberg, which can then be auto-forwarded to the developer in question, if applicable.
If a fundamental flaw is revealed in what the VST3 format allows, that should be patched.
We are bumping up against the predictions of complexity theory here–that paradoxically predictability goes out the window with systems this potentially complex. So Steinberg must get a handle on the pandora’s box it has opened for the sake of stability and performance.
VST was a game-changing format and created a whole new industry, but this industry has been notorious for failing to do things correctly at various times. I even remember when brainworx ¶ had a critical flaw in ALL of their VST3 plugins that they knew about but did not announce, because reasons. I only was able to isolate it by halving and halving again and again my plugins that would load, finally realizing that this one developer was responsible for ALL their plugins causing crashes! They acknowledged and fixed it about a month later. But the damage had been done: countless hours spent trying to isolate it, added stress, loss of sleep, etc.
The quality bar really must be raised in this industry, and I will keep hammering that point till those able to make necessary changes start to make them in earnest.
Hi Sebastian_Alvarez
Have you found a solution to your problem in the meantime? I’m having exactly the same difficulties. It affects all versions of Kontakt available here (5-8), as a plugin or standalone. The constant freezing makes meaningful work impossible and NI blocks all requests successfully (or with its terrible chatbot). The problem only seems to exist on the Mac (here: Macbook 2019/Intel with Sequia 15.5, Reaper-DAW), everything is ok on the PC. Would be great if you knew the solution …
Greetings Tommy
Sorry, Tommy, I’m afraid I can’t help you. I built a PC in January because the 64 GB of RAM in my Mac Studio wasn’t enough, and I haven’t even installed Cubase or Kontakt on the Mac once I wiped the internal drive to install Sequoia.
Thank you for your quick reply and good luck with the Studio PC! I will continue to look for a solution to the Kontakt freeze problem. Unfortunately, with this error, I can’t use the Mac for audio production, even though it was only intended for this purpose. 
But thankfully it works on the PC, even though I like the midi latency on the Mac better. It’s a pity that such serious errors can occur, NI is not a small company after all.
Thanks again and best regards
There’s one thing I remember about this bug. If I had been using Blender, and then at some point closed it and opened Cubase, then any Kontakt instrument, this bug would show up.
But if after working with Blender, I would reboot the Mac Studio and started working with Cubase and Kontakt, it would be fine. Now, I don’t know if you work with Blender or not, but if you do, a reboot might help with this. And if you don’t use Blender at all, then perhaps you might be using some other program that also causes this. I would suggest, unless you already tried this, that when you’re getting ready to work in Cubase, just give your Mac a reboot and see what happens. Maybe Blender and some other programs use some kind of API or whatever that down the road causes Kontakt to behave like this. The culprit is still most likely Kontakt because it’s ancient software that they keep throwing patches on top of, rather than completely modernize it.
An interesting hint, thank you! I don’t use Blender, but I do use other programmes of this kind. I’ll find out about that …
Unfortunately that’s true. And even the latest updates can only hide the fact that the underlying technology is quite antiquarian.