multiprocessing.Process generates FileNotFoundError when argument isn't explicitly referenced

Aperta
#94,765 18 commenti 9 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
python

Direzione di ricerca

Riproduci lo script fornito su Linux con il metodo di avvio spawn, quindi leggi multiprocessing/spawn.py e multiprocessing/synchronize.py in corrispondenza del traceback. Confronta l'argomento multiprocessing.Value inline con il valore referenziato esplicitamente e il comportamento di fork. Il lavoro è completato quando il FileNotFoundError segnalato è risolto o chiaramente documentato, con una copertura di regressione per il riproduttore.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

stdlib topic-multiprocessing type-bug

Bug report
This is a continuation for the possible bug mentioned in issue https://github.com/python/cpython/issues/82236 which was closed because DonnyBrown, the submitter, didn't provide enough information.

DonnyBrown was getting a FileNotFoundError when starting a process with multiprocessing.Process that uses an argument that doesn't have an explicit reference. I'm able to reproduce the same error using the test code DonnyBrown provided in that issue on Ubuntu Desktop LTS 22.04 x86-64 with CPython 3.10.4. @iritkatriel mentioned that they were unable to reproduce the error on Windows 10 with Python 3.10.

I can also reproduce the error using this slightly modified/simpler version of DonnyBrown's test code that I have been testing:

import multiprocessing

def demo(argument):
    print(argument)

if __name__=="__main__":
    multiprocessing.set_start_method("spawn") # Changing this to "fork" (on platforms where it is
                                              # available) can also cause the below code to work.


    process=multiprocessing.Process(target=demo, args=[multiprocessing.Value("i", 0)]) # FAILS

    #process=multiprocessing.Process(target=demo, args=[0])                            # WORKS

    #reference_To_Number=multiprocessing.Value("i", 0)                                 # WORKS
    #process=multiprocessing.Process(target=demo, args=[reference_To_Number])


    process.start()
    process.join()

The traceback I get with the above code is:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3.10/multiprocessing/spawn.py", line 116, in spawn_main
    exitcode = _main(fd, parent_sentinel)
  File "/usr/lib/python3.10/multiprocessing/spawn.py", line 126, in _main
    self = reduction.pickle.load(from_parent)
  File "/usr/lib/python3.10/multiprocessing/synchronize.py", line 110, in __setstate__
    self._semlock = _multiprocessing.SemLock._rebuild(*state)
FileNotFoundError: [Errno 2] No such file or directory

The above code can be made to work on my test system by making any of the following changes:

  • Change the process start method to "fork" instead.
  • Change the process argument to a simple integer instead of a multiprocessing.Value.
  • Assign the multiprocessing.Value to a variable and change the process argument to use the variable.

I'm not a Python expert so maybe this is the expected behavior when spawning a process directly with a multiprocessing.Value but it does seem odd that making any of the above mentioned changes causes the code to work or that (based on @iritkatriel's success with DonnyBrown's test code) running it on Windows 10 (which uses the "spawn" start method) will probably cause the code to work.

Your environment

  • CPython versions tested on: 3.10.4
  • Operating system and architecture: Linux, Ubuntu Desktop LTS 22.04, x86-64
Lingua principale
Python
Stelle
77.2k
Fork
36k
Merge medio
1g 9h
PR unite (30g)
558

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di python/cpython

Tutte le issue di python/cpython

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.