-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
server process of shared_memory shuts down if KeyboardInterrupt #80549
Labels
Comments
When starting a SharedMemoryManager in an interactive session, any KeyboardInterrupt event will be transmitted to the (sub)process running the shared memory server, which causes the Manager to be unusable thereafter: >>> from multiprocessing.managers import SharedMemoryManager
>>> smm = SharedMemoryManager()
>>> smm.start()
>>> start typing something wrong
KeyboardInterrupt
>>> sl = smm.ShareableList(range(10))
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/pierreglaser/repos/cpython/Lib/multiprocessing/managers.py", line 1342, in ShareableList
with self._Client(self._address, authkey=self._authkey) as conn:
File "/home/pierreglaser/repos/cpython/Lib/multiprocessing/connection.py", line 502, in Client
c = SocketClient(address)
File "/home/pierreglaser/repos/cpython/Lib/multiprocessing/connection.py", line 629, in SocketClient
s.connect(address)
FileNotFoundError: [Errno 2] No such file or directory I suggest ignoring SIGINT in the server process. |
pierreglaser
mannequin
added
3.8 (EOL)
end of life
type-crash
A hard crash of the interpreter, possibly with a core dump
labels
Mar 19, 2019
Your patch sounds good on the principle, but can you make a patch out of it? |
Sorry - I meant make a *PR* out of it :-) |
Done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: