11-20-2012, 12:38 AM
I'm just saying because it seems to me that you're heading in a direction slightly different than the vanilla algorithm.
The assertion is weird, it means that someone has put the cByteBuffer object into an invalid state (reading position is beyond buffer end - how did it get there without wrapping?) If you comment the assertion out, it won't stop the server immediately, but the server will crash soon afterwards without a warning, because memory is being overwritten where it shouldn't be.
I've been hunting that bug for quite some time and I thought I fixed it; it doesn't happen for me at all anymore.
The assertion is weird, it means that someone has put the cByteBuffer object into an invalid state (reading position is beyond buffer end - how did it get there without wrapping?) If you comment the assertion out, it won't stop the server immediately, but the server will crash soon afterwards without a warning, because memory is being overwritten where it shouldn't be.
I've been hunting that bug for quite some time and I thought I fixed it; it doesn't happen for me at all anymore.