Michael Lidgren

Not really. I plug pure bugs and small fixed, but no active development, no.

As far as I remember it was for performance; ConcurrentQueue was expensive, esp. when uncontested. It was a very long time ago tho; no idea if this is the case...

The code you pasted isn't part of the library... do you get this problem with the samples as well?

Can you verify setting UseMessageRecycling to false suppressed the problem?

Did you try UseMessageRecycling false? I also advice running in Debug as more checks are made there. I presume you are not manually recycling the message before it's read. I...

Aha. UnreliableSizeBehaviour.NormalFragmentation is a very suspect feature kept mostly for backwards compability. It should never really be used as it stands right now. I'm hoping to implement fragmentation for unreliable...

All pasted code is custom code so it's hard to tell if it's a library problem or local problem; and i'm not able to repro the issue...