06f64948d5
Motivation: We need to ensure we not allow calling set/writeCharsequence on an released ByteBuf. Modifications: Add test-cases Result: Proves fix of [#6951].