You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The unsafe setting of the LENGTH_OFFSET was setting the value as a long, whereas the actual field in the Java PooledByteBuf type is an int.
The order of updating the readerIndex before the writerIndex was causing the bounds check on the readerIndex call to fail as the writerIndex had not yet been corrected.
Correction of the above causes tests to pass consistently with Netty 4.1.32 (currently the latest version).
Netty 4.1.30 and above (plus earlier versions intermittently) fail the following test:
Two issues were identified in
ButeBufProxy:LENGTH_OFFSETwas setting the value as along, whereas the actual field in the JavaPooledByteBuftype is anint.readerIndexbefore thewriterIndexwas causing the bounds check on thereaderIndexcall to fail as thewriterIndexhad not yet been corrected.Correction of the above causes tests to pass consistently with Netty 4.1.32 (currently the latest version).
cc #90 #96 #111