Message396734
I was trying to reproduce the problem and can get the core dump to happen with a smaller program as well -- it doesn't seem related to asyncio specifically but seems to be a bug with multiprocessing.Event (or probably the primitives inside it).
```
#!/usr/bin/env python
import time
import multiprocessing
def master_func(event) -> None:
print(f"Child: {event = }")
print(f"Child: {event.is_set() = }") # Crashes here with SIGSEGV in sem_trywait
print("Completed")
if __name__ == "__main__":
event = multiprocessing.Event()
context_spawn = multiprocessing.get_context("spawn")
proc = context_spawn.Process(target=master_func, args=(event, ))
proc.start()
print(f"Parent: {event = }")
print(f"Parent: {event.is_set() = }")
proc.join()
```
Switching to fork instead of spawn bypasses the issue. Trying to dig into this a little bit more. |
|
Date |
User |
Action |
Args |
2021-06-29 14:29:49 | knl | set | recipients:
+ knl, asvetlov, yselivanov, Andrei Pozolotin |
2021-06-29 14:29:49 | knl | set | messageid: <1624976989.33.0.965241130066.issue43832@roundup.psfhosted.org> |
2021-06-29 14:29:49 | knl | link | issue43832 messages |
2021-06-29 14:29:49 | knl | create | |
|