New submission from JoshN:
Creating a socket in one thread and sharing it with another will cause the
socket to corrupt as soon as the thread it was created in exits.
Example code:
import socket, threading, time, os
def start():
a = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
a.bind(("", 8080))
a.set_inheritable(True)
thread = threading.Thread(target=abc, args=(a.fileno(),))
thread.start()
time.sleep(2)
print("Main thread exiting, socket is still valid: " + str(a) + "\n")
def abc(b):
sock = socket.socket(fileno=b)
for _ in range(3):
print("Passed as an argument:" + str(sock) + "\n=====================")
time.sleep(1.1)
start()
Note that, as soon as the main thread exits, the socket isn't closed, nor is
the fd=-1, etc. Doing anything with this corrupted object throws WinError 10038
('operation performed on something that is not a socket').
I should note that the main thread exiting doesn't seem to be the cause, it is
the original object containing the socket going out of scope that causes the
socket to become corrupted.
-JoshN
----------
components: IO
messages: 262951
nosy: JoshN
priority: normal
severity: normal
status: open
title: Socket state corrupts when original assignment goes out of scope
type: crash
versions: Python 3.5
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26703>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
