I just got an e-mail from the VSL support and they where not able to reproduce the problem. :(
I have contacted EastWest support now in hope of getting some information.
I don't know if its only PLAY but i had a hard time trying to get the same hang/crash with only Kontakt.
But the instance i but the plug-in Spaces on a Kontakt instance, i was able to crash it. And every time
i used an instance of Play (even a single instance) i was able to crach it withing 2-3 minutes. It might
be that Play and Spaces are in the habit of triggering the problem more rappidly than for instance Kontakt.
This was also on my slave so it did not become unstable because it was on the same machine as
the sequencer.
Ill report back when i hear from EW Support :)
EDIT: Im posting the tests i did. I also performed a test with Presonus Studio One v2, ended up with the same ressults.
TEST 1:
On the same computer as Cubase:
one instance of VEpro5 with only Play
one instance of VEpro5 with Kontakt and Spaces running.
Slave computer:
one instance of VEpro5 with only Kontakt
one instance of VEpro5 with Play, Kontakt, Spaces and Fabfilter
It seemed to work fine, then i clicked on the Audio Engine button on one of the instances that where
on the computer that Cubase is on and it crashed, just like it usually does, but just this time it seemed
like i forced it to crash rather it doing it randomly. I had 2 instances connected to this server and they
both died at the same time. The Slave computer followed closely after and crashed within a minute.