Quickly testing NoiseMaker on Windows 10…
I easily managed to completely break Noisemaker’s audio output by fiddling with the LFOs as you described.
It seems like whenever one LFO is connected to the other LFO’s modulation rate, it becomes highly sensitive to any additional LFO rate changes, and may catastrophically fail at any moment.
Happens both when fiddling with the GUI manually, or when rapidly changing the parameters using a Renoise LFO or some other modulation device.
I experienced various problems ranging from simple stuff like the audio going silent but the controls still working, all the way up to more extreme instances where the plugin just puked out 0dB hard clipped garbage that scared the shit out of me, hahah.
Sometimes the plugin audio failed but it didn’t really crash the GUI, while other times it crashed hard and Renoise became unresponsive. FYI: Enabling plugin sandboxing did seem to help contain the crash without bringing Renoise down with it.
I also quickly tested stuff in Ableton Live 9 and managed to cause the plugin audio to die there, but it didn’t totally crash on me yet.
Either way, we could try to see if it’s possible to handle the crash more gracefully somehow, but the core issue here is definitely a problem within NoiseMaker itself. There’s a really nasty bug lurking somewhere in its modulation system, I guess…