[netsend] cause plugdata crash

[mimicras]

Any correct use of [netsend] cause plugdata (app.) to crash. Any (allowed) port and address (localhost or 127…) or external (192…) cause crash. The best way to check this is just open help for [netsend] and run :)

I think this is much harder to catch …

best,

m.

[mimicras]

Maybe it helps: The same thing on Linux (Mint 22 Wilma, Ubuntu 24.04 noble) does not crash but reports in Console: Connection reset by peer (104) And on next try: Connection refused (111)

best,

m.

[dromer]

The same thing on Linux

What is the OS in the first post then?

[mimicras]

First time tested on MacOS (three different computers with BigSur (11.6.5 - M1) and High Sierra and Sierra (Intel Macs). Also with Universal and Legacy versions of plugdata. The problem could be also with [netreceive]. I will try to do more test to point right object.

[mimicras]

Here are more. Adding a -u flag will not cause crash, but there are no communication still. I created similar patch in MaxMSP and and when sending from Max to plugd - no communication, no crash Sending from plugd to Max - two errors in Max:

• OSC bad message name string: DataAfterAlignedString Unreasonably long string. Dropping
  and
• OSC packet size (5) not a multiple of 4 bytes. Dropping.

I am not expert in this, but to me it looks like instead of actual data plugd is sending some variable name or other elements of opcode…

If there is any more I can test - let my know.

[jamshark70]

Sending from plugd to Max - two errors in Max:

OSC bad message name string: DataAfterAlignedString Unreasonably long string. Dropping and OSC packet size (5) not a multiple of 4 bytes. Dropping.

Max's [udpreceive] expects an OSC-formatted message, so in plugdata, it has to be [oscformat] --> [netsend -u -b] -- Max won't understand it otherwise.