Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Sockets leak
See original GitHub issueA socket opened in OrientSocket.__init__ method is replaced for nothing with a new one in OrientSocket.connect method. So the socket opened in OrientSocket.__init__ is wasted and remains unclosed.
Moreover, in OrientDB class there is no way to close underlying OrientSocket (it is only closed in case of some error).
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Closing non-blocking socket causes leak - Microsoft Learn
It appears to be a memory and thread handle leak. Cause. Sockets may be shut down in either a graceful or abortive manner....
Read more >Closing Sockets and Avoiding Resource Leaks - Documentation
If you forget to close a socket using closesocket() , then its resources remain in use by the system. Resource leaks, like memory...
Read more >Socket leaks - Digi International
There are instances where a socket leaks when closing a connection while there is pending RX data. This state is reported whenever the ......
Read more >Strange network socket leak in Java app - Stack Overflow
CLOSE_WAIT means that the connection has been closed by the remote peer but the socket is waiting for the local application to close...
Read more >Sockets leak, a case study - Java mon amour
Sockets leak, a case study. We get a "too many files open", and lsof reveals some 40k IPv6 connections. What happens if you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Merged
The failures. I’ve to fix them, maybe they are related to some changes in OrientDB.