On Windows, some plugins are not capable running on a multi-cpu environment.
For that reason a switch has been added to the vst-cachelist to disable multi-cpu for specific plugins.
New plugins are by default multi-cpu enabled.
I don’t specifically know if the trigger is also being applied on Mac environments as i know that Renoise was at least not capable of shutting down one of both cores. (This does not necessarily mean that it won’t be able to tie the VST just only to the first processor.)
The quickest thing you can try is to manually disable multi-core for Renoise completely and see if that gives any improvements to the plugin itself before it is worth it to mangle with the cache list.
Just tested this and it works just fine here. Does it always overload or only when you do something special?
Yes, but multi-cpu specific problems only occur when running several instances of the same plug. charly tried only one instance?
Also those problems should be rare these days with new plugs. Nearly every developer has multi core CPUs, many hosts support multi CPU processing these days…