diff options
| author | Jameson Nash <vtjnash@gmail.com> | 2023-10-02 15:15:18 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-02 15:15:18 +0200 |
| commit | c03569f0df3bb26e7e7bec9feabd9ae3c372568e (patch) | |
| tree | a2c4fe43bd9eead474549967e909879ff2490237 /test/test-tcp-shutdown-after-write.c | |
| parent | 2a4cab70ef0133fe3b06b8844eb4541fbab5f826 (diff) | |
| download | libuv-c03569f0df3bb26e7e7bec9feabd9ae3c372568e.tar.gz libuv-c03569f0df3bb26e7e7bec9feabd9ae3c372568e.zip | |
win,process: avoid assert after spawning Store app (#4152)
Make sure this handle is functional. The Windows kernel seems to have a
bug that if the first use of AssignProcessToJobObject is for a Windows
Store program, subsequent attempts to use the handle with fail with
INVALID_PARAMETER (87). This is possilby because all uses of the handle
must be for the same Terminal Services session. We can ensure it is
tied to our current session now by adding ourself to it. We could
remove ourself afterwards, but there doesn't seem to be a reason to.
Secondly, we start the process suspended so that we can make sure we
added it to the job control object before it does anything itself (such
as launch more jobs or exit).
Fixes: https://github.com/JuliaLang/julia/issues/51461
Diffstat (limited to 'test/test-tcp-shutdown-after-write.c')
0 files changed, 0 insertions, 0 deletions