Skip to content
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

bpo-35267: warning deadlock in multiprocessing.Pool #11143

Closed
wants to merge 1 commit into from

Conversation

@Windsooon
Copy link
Contributor

commented Dec 13, 2018

@ZackerySpytz

This comment has been minimized.

Copy link
Contributor

commented Dec 13, 2018

The issue number is wrong.

@Windsooon Windsooon changed the title bpo-35367: warning deadlock in multiprocessing.Pool bpo-35267: warning deadlock in multiprocessing.Pool Dec 13, 2018

@Windsooon

This comment has been minimized.

Copy link
Contributor Author

commented Dec 13, 2018

Thank you @ZackerySpytz, I updated it.

@ZackerySpytz

This comment has been minimized.

Copy link
Contributor

commented Dec 13, 2018

Not quite. Please also fix the commit message and the link in the first post.

@Windsooon Windsooon force-pushed the Windsooon:bpo-35267 branch from 7337e32 to f1cf7fe Dec 13, 2018

@vstinner
Copy link
Member

left a comment

I would prefer to see the issue fixed rather than documented.

@bedevere-bot

This comment has been minimized.

Copy link

commented Dec 14, 2018

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@Windsooon

This comment has been minimized.

Copy link
Contributor Author

commented Dec 14, 2018

@vstinner any ideas to fix it?

@vstinner

This comment has been minimized.

Copy link
Member

commented Dec 14, 2018

@vstinner any ideas to fix it?

Sorry, I have no idea.

@Windsooon

This comment has been minimized.

Copy link
Contributor Author

commented Dec 17, 2018

I don't know how to fix it. As Nathaniel J. Smith said:

you might be thinking of PIPE_BUF, which POSIX says has to be >= 512 bytes, and on linux is 4096 bytes. This a magic number where if you send < PIPE_BUF bytes in a single write, then the kernel isn't allowed to break it up into pieces. This means that if you have a non-blocking pipe, then select can only report it as being writable if it as at least PIPE_BUF bytes of free space available.

Some new ideas are needed.

@csabella csabella requested a review from pitrou Jun 5, 2019

@JulienPalard

This comment has been minimized.

Copy link
Member

commented Sep 13, 2019

As said here by Victor and in b.p.o by Davin, there may be a fix, so we better work on fixing it than documenting the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.