Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ResourceWarnings about unclosed sockets #254

Open
twm opened this issue May 27, 2018 · 0 comments
Open

ResourceWarnings about unclosed sockets #254

twm opened this issue May 27, 2018 · 0 comments
Labels

Comments

@twm
Copy link
Owner

twm commented May 27, 2018

Observed while checking feeds in development:

<4>[twisted.logger._global] /usr/lib/python3.5/urllib/parse.py:360: builtins.ResourceWarning: unclosed <socket.socket fd=41, family=AddressFamily.AF_INET, type=2049, proto=0, laddr=('...', 45076), raddr=('...', 80)>
<4>[twisted.logger._global] /usr/lib/python3.5/urllib/parse.py:360: builtins.ResourceWarning: unclosed <socket.socket fd=43, family=AddressFamily.AF_INET, type=2049, proto=0, laddr=('...', 40292), raddr=('...', 443)>
<4>[twisted.logger._global] /usr/lib/python3.5/urllib/parse.py:360: builtins.ResourceWarning: unclosed <socket.socket fd=22, family=AddressFamily.AF_INET, type=2049, proto=0, laddr=('...', 45072), raddr=('...', 80)>

The file and line listed for the warning don't seem to have any real meaning. Presumably that is just where garbage collection was triggered.

This is concerning because these sockets most likely originate somewhere within feedparser or one of the libraries it uses. Could this be kurtmckee/feedparser#107?

@twm twm added the bug label May 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant