-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Deadlock in reading stdout from cmd #22832
Comments
StefanKarpinski
added
bug
Indicates an unexpected problem or unintended behavior
io
Involving the I/O subsystem: libuv, read, write, etc.
labels
Jul 16, 2017
vtjnash
added a commit
that referenced
this issue
Jul 20, 2017
when calling uv_shutdown on a handle being written to by another process we might never get the UV__POLLOUT notification but we also don't need to delay the uv_close call if we have nothing to write in the future, we should introduce a new `uv_drain` callback, instead of continuing to abuse uv_shutdown for this purpose fix #22832
vtjnash
added a commit
that referenced
this issue
Jul 20, 2017
when calling uv_shutdown on a handle being written to by another process we might never get the UV__POLLOUT notification but we also don't need to delay the uv_close call if we have nothing to write in the future, we should introduce a new `uv_drain` callback, instead of continuing to abuse uv_shutdown for this purpose fix #22832
vtjnash
added a commit
that referenced
this issue
Jul 20, 2017
when calling uv_shutdown on a handle being written to by another process we might never get the UV__POLLOUT notification but we also don't need to delay the uv_close call if we have nothing to write in the future, we should introduce a new `uv_drain` callback, instead of continuing to abuse uv_shutdown for this purpose fix #22832
vtjnash
added a commit
that referenced
this issue
Jul 21, 2017
when calling uv_shutdown on a handle being written to by another process we might never get the UV__POLLOUT notification but we also don't need to delay the uv_close call if we have nothing to write in the future, we should introduce a new `uv_drain` callback, instead of continuing to abuse uv_shutdown for this purpose fix #22832
visr
added a commit
to visr/LasIO.jl
that referenced
this issue
Jul 26, 2017
…n't dead lock. Ugly workaround." This reverts commit 2a5c158. Issue JuliaLang/julia#22832 is fixed with JuliaLang/julia#22886
vtjnash
added a commit
that referenced
this issue
Jul 28, 2017
fix an IO deadlock condition (#22832) disabled test seems to indicate this doesn't fix it fully, but it seems that only reproduces on CI, not on any of my local machines
visr
added a commit
to visr/LasIO.jl
that referenced
this issue
Aug 2, 2017
…n't dead lock. Ugly workaround." This reverts commit 2a5c158. Issue JuliaLang/julia#22832 is fixed with JuliaLang/julia#22886
Closed
visr
added a commit
to visr/LasIO.jl
that referenced
this issue
Aug 17, 2017
…n't dead lock. Ugly workaround." This reverts commit 2a5c158. Issue JuliaLang/julia#22832 is fixed with JuliaLang/julia#22886
visr
pushed a commit
to visr/julia
that referenced
this issue
Sep 15, 2017
when calling uv_shutdown on a handle being written to by another process we might never get the UV__POLLOUT notification but we also don't need to delay the uv_close call if we have nothing to write in the future, we should introduce a new `uv_drain` callback, instead of continuing to abuse uv_shutdown for this purpose fix JuliaLang#22832
visr
added a commit
to visr/julia
that referenced
this issue
Sep 15, 2017
visr
pushed a commit
to visr/julia
that referenced
this issue
Sep 15, 2017
when calling uv_shutdown on a handle being written to by another process we might never get the UV__POLLOUT notification but we also don't need to delay the uv_close call if we have nothing to write in the future, we should introduce a new `uv_drain` callback, instead of continuing to abuse uv_shutdown for this purpose fix JuliaLang#22832
vtjnash
added a commit
to vtjnash/julia
that referenced
this issue
Jun 8, 2018
let's hope it passes and doesn't just hang...
vtjnash
added a commit
that referenced
this issue
Jun 8, 2018
let's hope it passes and doesn't just hang...
vtjnash
added a commit
that referenced
this issue
Jun 8, 2018
let's hope it passes and doesn't just hang...
vtjnash
added a commit
that referenced
this issue
Jun 8, 2018
let's hope it passes and doesn't just hang...
vtjnash
added a commit
that referenced
this issue
Jun 19, 2018
let's hope it passes and doesn't just hang...
vtjnash
added a commit
that referenced
this issue
Jun 25, 2018
let's hope it passes and doesn't just hang...
vtjnash
added a commit
that referenced
this issue
Jun 25, 2018
ararslan
pushed a commit
that referenced
this issue
Jul 2, 2018
when calling uv_shutdown on a handle being written to by another process we might never get the UV__POLLOUT notification but we also don't need to delay the uv_close call if we have nothing to write in the future, we should introduce a new `uv_drain` callback, instead of continuing to abuse uv_shutdown for this purpose fix #22832 Ref #22886 (cherry picked from commit 8949a95)
ararslan
pushed a commit
that referenced
this issue
Jul 2, 2018
jrevels
pushed a commit
that referenced
this issue
Jul 2, 2018
vtjnash
added a commit
that referenced
this issue
Feb 5, 2021
vtjnash
added a commit
that referenced
this issue
Apr 2, 2021
vtjnash
added a commit
that referenced
this issue
Jun 2, 2021
shirodkara
pushed a commit
to shirodkara/julia
that referenced
this issue
Jun 9, 2021
johanmon
pushed a commit
to johanmon/julia
that referenced
this issue
Jul 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I want to read the stdout from an external program and process the results in Julia. However it sometimes hangs indefinitely.
It was previously discussed on Discourse, but @vtjnash suggested to make an issue here, he could reproduce it by running this on all cores (I also see it on one core):
It just reads in two MiB of zeroes, in two blocks.
Successful iterations of the loop will print this to stderr:
Until it hangs. Killing it with Ctrl-C then gives the following:
As noted on Discourse, when using smaller block sizes, it always seems to hang after 65536 (2^16) bytes. This is seen on julia 0.5/0.6/master and all OS, though on Unix it seems to happen more quickly than Windows.
@vtjnash said that it seems like something is dropping an event notification.
cc @evetion
The text was updated successfully, but these errors were encountered: