Are you sure your OSC packets are not too long? (< 8192 bytes)no
we have been sending the following kind of messages: client to client messages that were strings cluped in 200 char size strings. server to client notifications (small, but possibly many from many servers) one thing I could imagine that an OSCResponder might be recieving too many messages in a short time. It creates an OSCresponder objectfor every message it recieves (for the lookup), so maybe there is too many objects.
we are using OSCresponders with a nil address so that might be part of the problem, too.
On Nov 30, 2003, at 4:11 AM, Julian Rohrhuber wrote:when having many incoming osc messages on client side (OSCresponder), we get irregular crashes that look like a buffer overflow. I'll try to reproduce the problem later.
-- .