Delilah Lewis comments

Results 7 comments of


                                            Delilah Lewis

transport: handler server transport continuously reads from streams without waiting for application

![leak](https://github.com/grpc/grpc-go/assets/44428616/cb00373e-b145-4c73-aa6b-da7cabbecb64)

transport: handler server transport continuously reads from streams without waiting for application

@arjan-bal Thank you for your response. Even after switching to gRPC v1.64.0, I am still encountering the same problem.

transport: handler server transport continuously reads from streams without waiting for application

This is the test code and a screenshot of its pprof results [grpc_client_stream_example.zip](https://github.com/grpc/grpc-go/files/15431988/grpc_client_stream_example.zip) ![image](https://github.com/grpc/grpc-go/assets/44428616/dbd620c0-764d-4ce4-9b3e-66e43863aa50) ![image](https://github.com/grpc/grpc-go/assets/44428616/879d3974-ea1c-46e9-b4af-b86c36261b80) ![image](https://github.com/grpc/grpc-go/assets/44428616/fb02a62a-cd3d-431d-a541-7b88a6c858ea)

transport: handler server transport continuously reads from streams without waiting for application

@arjan-bal

transport: handler server transport continuously reads from streams without waiting for application

Perhaps I didn't make it clear earlier. The example code above was just for testing. The actual scenario is that the client sends a large amount of data through the...

transport: handler server transport continuously reads from streams without waiting for application

Thanks, I now know that ServerTransport has two implementations. Why is serverHandlerTransport asynchronous and what are the restrictions?

transport: handler server transport continuously reads from streams without waiting for application

Thank you very much for your answer. Now I have changed the listener to grpc.