Michael Lumish

@i7N3 Have you checked whether this happens when running the client and server on the same machine. If it does, a complete reproduction would really help me track down the...

This has been resolved. In current versions of the library, these errors now additionally show the stack trace of the start of the call.

You linked to this issue instead of your proof of concept. If you're injecting the connection using credentials as mentioned in the earlier comment, that is an unintended hack that...

One option I see would be to introduce a new `Channel` factory or constructor that takes a stream instead of a target address. This is probably the cleanest way to...

@nptri This issue is almost two years old, and there have been substantial relevant changes to grpc-js in the meantime. If you are still experiencing the same problem on the...

If you provide a code snippet that demonstrates the leak, I would be happy to investigate.

What version of `@grpc/grpc-js` are you using? And what is your memory limit? Or alternatively, what is the average memory growth rate you are observing?

You might want to try updating to the latest version (1.8.3). A significant amount of the relevant code has been reworked/refactored since 1.6.10.

@Matt-Esch Can you file a separate issue with the details of the problem you are seeing? Retries were introduced after this issue was filed so a retry-specific problem is a...

@Matt-Esch The expectation with `ChannelzCallTracker` is that there should be one per channel, one per server, and a couple per open connection. In other words, quite a few, but proportional...