Rapidly cancelling a Call can overwhelm transport
Abierto
performance
- Lenguaje dominante
- Java
- Estrellas
- 12.1k
- Forks
- 4k
- Merge medio
- 2 d 17 h
- PR fusionados (30 d)
- 37
Descripción
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.
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.