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
Race condition with close() in multiple threads #11144
Comments
From @cpansproutCommit 2e0c6a16 (the fix for 78494) causes a new race condition. Up till now, there has already been a race condition when two threads close() the same handle. Either one thread or the other would get the exit status, but not both. It was never predictable which thread would get it. Now, there is the slight possibility that *neither* thread will receive the exit status. I believe any code that runs into this is already buggy, as, in 5.13.9 and earlier, close() in one thread blocks until close is called in every other thread (provided the pipe was open when the threads were created, and got cloned as a result). So I think this bug is acceptable for 5.14, as fixing it would require no small amount of code restructuring. Flags: Site configuration information for perl 5.13.9: Configured by sprout at Sat Feb 12 14:34:11 PST 2011. Summary of my perl5 (revision 5 version 13 subversion 9) configuration: Locally applied patches: @INC for perl 5.13.9: Environment for perl 5.13.9: |
From @cpansproutOn Sun Feb 20 13:09:43 2011, sprout wrote:
It is actually commit 2e0cfa1. |
@cpansprout - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#84496 (status was 'open')
Searchable as RT84496$
The text was updated successfully, but these errors were encountered: