My error in MUX VSTi, caused by Flowstone-can anyone shed any light on it

[nix808]

Heya,
My host Orion doesn't like Flowstone's Ruby implementation,
so I am looking for a host as VST to use as a bridge.
So I have some bug due to my VST building environment Flowstone.
Anyway, I wish to keep working in Orion,
and have just tried MUX.
After about 2 minutes, MUX locks up and gives me this error->

It doesn't crash Orion though.
Can this give me a clue as to what in FS is awry?
Like I say, this is not my programming error, but Flowstone's.
However if this can shed any light on the bug,
I will pass it on to RDSP.
Cheers peeps,
I would have acquired a MUX license, but for this.

[MuTools]

When exactly did this alert popup? After simply pluggin in MUX Vst into Orion? Or after inserting a Flowstone generated plug into MUX Vst?

[nix808]

I imagine that MUX generally runs fine in Orion,
it is after inserting 2 different FS plugs,
and playing a single note on each for 1 minute,
within MUX VSTi loaded in Orion 8.5 full.
I will rename my original post to reflect this, sorry.
The plugs contain 1 instance each of a Ruby timer code.
I can up the code if you'd like to see it.
In my tests I have found that only Ruby generates crashes.
I imagine that if I take away the 2 code modules,
the plugs will run fine.
My Windows is Windows 7 Professional 64-bit service pack 1.
I can send the FS schematic too.
It's not really your problem, so sorry,
but if the loop message tells you anything, I would be keen to hear.
Thanks for the response, and I will edit the topic name now.
Cheers, Nick- Phonics

[MuTools]

Unfortunately i can't help in analysing/debugging Ruby code. I have too much work myself too. But maybe as a helpful hint i can tell you that that MUX alert ("Internal thread loop time out") most probably comes because the audio processing thread is blocked in some way, which may also be the reason why Orion crashes when you use the Ruby plug directly in Orion.