Rapidly cancelling a Call can overwhelm transport
Open
performance
- Dominant language
- Java
- Stars
- 12.1k
- Forks
- 4k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 37
Description
Doing something like
```
ClientCall call = channel.newCall(foo, CallOptions.DEFAULT);
call.start(listen, new Metadata());
call.sendMessage(null);
call.halfClose();
call.request(1);
call.cancel();
```
rapidly in a loop causes memory to not get reclaimed. Somehow netty is holding on to commands sent to it from the ClientCallImpl.
Contributor guide
Assessment
This issue has not been assessed yet.