Attempt to fix port leak, also fixed clean up of sockets. #1

Merged
merged 1 commit into from Jul 9, 2012

Projects

None yet

2 participants

@hirotnk

There is a possibility of port leak when processes are killed using exit/2 BIF when they are connecting/closing sockets, executing in prim_inet module.
Also fixed the format of remaining free sockets in terminate/2.

Yoshihiro Tanaka Attempt to fix port leak, also fixed clean up of sockets.
There is a possibility of port leak when processes are killed using exit/2 BIF when they are connecting/closing sockets, executing in prim_inet module.
Also fixed the format of remaining free sockets in terminate/2.
70fd653
@ferd
Owner

Ah, so if I get it right, the fix I originally sent by mail fixed only half the problem -- there's still a delay before the socket is set up right?

I'm a bit busy (participating in Spawnfest), so I'll try to manually merge it (can't be done automatically) first thing Monday morning, and then create a new tag for everyone to have a stable version.

@hirotnk

Yes, some of then are slow. Thank you for the comment, good luck on Spawnfest !!

@ferd ferd merged commit 70fd653 into ferd:socket-leak Jul 9, 2012
@ferd
Owner

Hi, the change is finally merged in, back into master. I've also made a new tag with 1.2.8 containing that specific fix if you want everything to be stable.

Thanks again for the helpful reports, finding the bug, and completing the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment