I can confirm the crashes and have found that the playing position is reported at intervals of 60 ms. So it's not really a "flood" of data. Seems strange to me that javascript can't handle this.

Please to post or send a frozen device which exhibits the problem. Thanks, Jeremy

Ok, give me a day or so to isolate an example - just fyi, I've done a bit more testing and it seems to be no problem if I'm not outputting to the max windows - currently, my devices output a load of trace, maybe 10 msgs per update per clip for 4 clips - if i turn off the trace to the max window it seems to be ok - also, when running in live and not in the editor it's fine also, so maybe it's an issue with so much data going to the max window??

That doesn't seem likely, but we often see memory corruption problems which lead to crashes during posts to the Max window. That is, it's the effect and not the cause. Thanks for taking the time to isolate an example -- hopefully we can quickly identify the problem.

Best, Jeremy

ok, will do... where should I send the device to?

If you don't want to post it here, you can send it to my first name at cycling74 dot com.

Best, Jeremy