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
When an interceptor closes the call, the reactive subscription is not cancelled. This means that any resource allocated for a call are not removed, either, and effectively leak.
To circumvent this, I think the library should listen ServerCall.Listener.onComplete and ServerCall.Listener.onCancel, and cancel its subscription of the reactive sequence in reaction to it (if the sequence hasn’t completed yet).
The text was updated successfully, but these errors were encountered:
@rmichela thank you for reviewing & merging so quickly! Do you have the chance to publish a release? We’d like to profit from the changes as soon as possible.
When an interceptor closes the call, the reactive subscription is not cancelled. This means that any resource allocated for a call are not removed, either, and effectively leak.
To circumvent this, I think the library should listen
ServerCall.Listener.onComplete
andServerCall.Listener.onCancel
, and cancel its subscription of the reactive sequence in reaction to it (if the sequence hasn’t completed yet).The text was updated successfully, but these errors were encountered: