Michael Lumish

I made that change based on the information provided. You showed a screenshot with a single retainer, so I took action regarding that single retainer. Does your heapdump still show...

The stream flow is connected to the stream returned by the gRPC API. If you have that stream in flowing mode and you are still experiencing this leak, then there...

I think I see the issue. Normally the API-level stream flow is connected to the http2 stream by a cycle of the API-level stream requesting a message, and the http2...

Do you think #1652 is related to this leak, or is it just another problem you are having?

First, I have released #2193 in grpc-js version 1.6.10. > I suspect that the double free is triggered by cancel and that the fix put in place triggers it more...

I want to hold off on this. Based on some other stuff we're looking at, we may not end up making these changes now, and in that case I would...

This should be fixed in version 1.6.9. Please try it out.

We have prioritized feature work based on what features we were aware of our users using. The grpc-js project has existed for 3 years and as far as I know...

I'm sorry for not communicating that more effectively. I mentioned it in the [1.0 announcement blog post](https://grpc.io/blog/grpc-js-1.0/), but I don't know how many people saw that. Other than that, I...

Compression support in grpc-js has been expanded in the 1.5.x release: clients can now send compressed messages, and servers can now receive compressed messages. Support for sending compressed messages from...