[Webkit-unassigned] [Bug 205280] Python 3: Multiprocessing doesn't do well when nested
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Dec 16 15:41:32 PST 2019
https://bugs.webkit.org/show_bug.cgi?id=205280
--- Comment #4 from Jonathan Bedard <jbedard at apple.com> ---
(In reply to Alexey Proskuryakov from comment #3)
> In Python 3, one can choose the underlying method for how multiprocessing
> works, it's called "start method". See
> <https://docs.python.org/3/library/multiprocessing.html>.
>
> As this bug is about multiprocessing having some strange behavior on tests
> with Python 3, it's relevant which of the methods you are using. I'm
> guessing that it is 'spawn' because that's the default. Since 'fork' was the
> only one that Python 2 supported, that would be the 1:1 replacement, but of
> course we shouldn't be using that on macOS.
I wasn't aware of this.
I haven't modified the start method used, so yes, it should be using spawn. Seems possible that the spawn/fork difference is the root of our problem, but I'm still at a loss as to why I saw a race condition.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20191216/666d6c32/attachment.htm>
More information about the webkit-unassigned
mailing list