Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@aaugustin
Copy link
Contributor

When connecting through a socks proxy to a non-existing or non-functional server such as example.com with the trio implementation, a warning is raised:

ResourceWarning: unclosed <socket.socket fd=15, family=2, type=1, proto=0, laddr=('127.0.0.1', 63402)>
  import gc; gc.collect()
Object allocated at (most recent call last):
  File "python-3.13/lib/python3.13/site-packages/trio/_socket.py", lineno 381
    stdlib_socket = _stdlib_socket.socket(family, type, proto, fileno)

This is the same issue with trio as 2e4f5ca was with asyncio.

When connecting through a socks proxy to a non-existing or non-functional server such as `example.com` with the trio implementation, a warning is raised:

```
ResourceWarning: unclosed <socket.socket fd=15, family=2, type=1, proto=0, laddr=('127.0.0.1', 63402)>
  import gc; gc.collect()
Object allocated at (most recent call last):
  File "python-3.13/lib/python3.13/site-packages/trio/_socket.py", lineno 381
    stdlib_socket = _stdlib_socket.socket(family, type, proto, fileno)
```

This is the same issue with trio as 2e4f5ca was with asyncio.
@codecov-commenter
Copy link

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

@aaugustin
Copy link
Contributor Author

This time I checked if the other implementations are vulnerable to the same issue.

It looks like they aren't — or at least it's their responsibility not ours ;-) Other than in asyncio and trio, we create the socket directly with a high-level API; we don't do the create/bind/connect sequence.

@aaugustin
Copy link
Contributor Author

I double-checked and tested that sock.close() is correct here — no await, no aclose.

@romis2012 romis2012 merged commit 4555b27 into romis2012:master Jul 31, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants