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 onNext method can be called from a non SDK owned thread, and if we allocate
the ByteBuf using the pooling allocator, then we pollute the customer's thread
with a ThreadLocal.
Using Unpooled#wrappedBuffer avoids actually copying the arrays so this should
be more performant as well.
Fixes#1133
"description": "Fix a bug that could pollute non SDK threads with `ThreadLocal`'s when allocating memory. See [#1133](https://github.com/aws/aws-sdk-java-v2/issues/1133)"
Copy file name to clipboardExpand all lines: http-clients/netty-nio-client/src/main/java/software/amazon/awssdk/http/nio/netty/internal/NettyRequestExecutor.java
0 commit comments