21 Apr
2015
21 Apr
'15
9:25 a.m.
On 2015-04-21 00:52, Jonathan Wilkes via Pd-list wrote:
Anyway it's trivial to fix-- again, I was just curious why I cannot trigger a corruption at all, even when flooding the socket with messages that have a large percentage of multi-byte characters.
because a localhost connection has an MTU of 65536 bytes and in practice nothing will re-packetize unless this boundary is hit.
so to trigger the problem reliably, make your message >65536 bytes and have your multibyte character occupy bytes 65536 and 65537.
fgmasdr IOhannes