Skip to content

fix or slow down windows socket leak#13604

Merged
jtattermusch merged 1 commit intogrpc:masterfrom
yayaboring:master
Dec 13, 2017
Merged

fix or slow down windows socket leak#13604
jtattermusch merged 1 commit intogrpc:masterfrom
yayaboring:master

Conversation

@yayaboring
Copy link
Copy Markdown
Contributor

related issue
#13519
#13102

@thelinuxfoundation
Copy link
Copy Markdown

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.

After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

Regards,
The Linux Foundation CLA GitHub bot

@grpc-testing
Copy link
Copy Markdown

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]


****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]



@grpc-testing
Copy link
Copy Markdown

[trickle] No significant performance differences

@grpc-testing
Copy link
Copy Markdown

[microbenchmarks] No significant performance differences

@jtattermusch
Copy link
Copy Markdown
Contributor

@yang-g, can you take a look?

@jtattermusch jtattermusch requested a review from yang-g December 12, 2017 00:31
@yayaboring
Copy link
Copy Markdown
Contributor Author

yayaboring commented Dec 13, 2017

similar code on server side.

wsa_success = WSAGetOverlappedResult(sock, &info->overlapped,

@jtattermusch
Copy link
Copy Markdown
Contributor

Known test failures:
#13122

Copy link
Copy Markdown
Contributor

@jtattermusch jtattermusch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for fixing!

@jtattermusch
Copy link
Copy Markdown
Contributor

It might be a good idea to backport this into 1.8.1.

This was referenced Dec 13, 2017
@smflorentino
Copy link
Copy Markdown

+1, thanks for fixing & backporting - our services are being impacted by this because gRPC attempts to connect to IPv6 first and fails (our service only exposes an IPv4 endpoint) - so every channel creation leaks a socket. When is 1.8.1 going to be released?

jtattermusch added a commit that referenced this pull request Dec 13, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants