-
Notifications
You must be signed in to change notification settings - Fork 769
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
AssignProcessToJobObject: (87) The parameter is incorrect. #1118
Comments
We saw this during early development, but were never able to reproduce it except on one machine in debug mode. Is there anything interesting about your machine? Extra anti-virus? Do other node-related processes work? I assume VS Code works otherwise. |
Hey. I found a thread that I might have a bad download and that I should uninstall, then delete the file from ".vscode" file from the user/%username%/.vscodefile. After I did that and re-installed. I had notifications appear. You should reload vscode (or) You should reload window. I did vscode reload everytime. After I posted this; I hit reload window and everything seems to be fine. I included strange events in txt file (attached) and a screen of what I think my processes were at the time. I'll try to recreate and update this thread asap. If things stay fine and we cant come up with anything relevant I'll close the issue. |
Just reinstalled the extensions, no error yet. I use python formatter black, I have it installed globally so I didn't think I needed to install, but vscode asked me if I wanted to reinstall. Said yes. Seems to be working again. #fingerscrossed |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I meet the same problem after I upgrade to 2021.6.0 version. Then I downgrade to 2021.5.4, the error doesn't show. OS and version: Windows 10 Home, Version: 1909, OS Build: 18363.1556 |
This is a month old closed issue. Please file a new issue with the template filled out; the python logs would also be helpful. |
Log output
Update: False alarm, there was a config issue due to a renamed VSCode workspace file. |
I'm curious about this; can you elaborate on this? What was incorrect and what did you do to fix it? We haven't had a way to reproduce this since we first saw it. |
The workspace file was rename from, let's say, I fixed my issue by opening VsCode with the new workspace file. This probably won't help anyone else though :( |
Yeah, unfortunately not; I can't see how a VS Code specific file would cause this odd node+Windows failure; it's not the same process. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
We can't reproduce this, so I don't know how we can fix it. As far as I can tell, it happens only on some Windows machines and only rarely. VS Code has also updated their version of Node, which I'm hoping fixed this in the meantime. |
This looks to me like a kernel bug, but I have found a workaround for this issue for programs that use libuv, such as VSCode / nodejs: libuv/libuv#4152 The procedure to reproduce it are to:
|
Thanks @vtjnash for looking into this issue and addressing it! didn't realize windows store app would be the trigger and successive CreateProcess calls would be affected. I was trying to get a minimal repro but now I see why that didn't work microsoft/vscode#186912 (comment) |
I was fortunate to have been given a much smaller reproducer. I only found this issue because I was searching for people who had solutions to it, and only came across a few places where people had had the same problem. Do you have a contact in the kernel team to ask whether they could see if this is a kernel issue or whether they could add a clarification to the documentation for AssignProcessToJobObject about this case? |
Don't have any known contacts, but I can ask around. |
Environment data
Expected behaviour
Vs Code to start without python server crashing.
Actual behaviour
The Python Tools server crashed 5 times in the last 3 minutes. The server will not be restarted.
Logs
Python language Server Output:
[Info - 11:55:56 AM] Pylance language server 2021.3.4 (pyright ba71f257) starting
[Info - 11:55:56 AM] Server root directory: c:\Users\Owner.vscode\extensions\ms-python.vscode-pylance-2021.3.4\dist
AssignProcessToJobObject: (87) The parameter is incorrect.
[Info - 11:55:57 AM] Connection to server got closed. Server will restart.
[Info - 11:55:57 AM] Pylance language server 2021.3.4 (pyright ba71f257) starting
[Info - 11:55:57 AM] Server root directory: c:\Users\Owner.vscode\extensions\ms-python.vscode-pylance-2021.3.4\dist
AssignProcessToJobObject: (87) The parameter is incorrect.
[Info - 11:55:58 AM] Connection to server got closed. Server will restart.
[Info - 11:55:58 AM] Pylance language server 2021.3.4 (pyright ba71f257) starting
[Info - 11:55:58 AM] Server root directory: c:\Users\Owner.vscode\extensions\ms-python.vscode-pylance-2021.3.4\dist
AssignProcessToJobObject: (87) The parameter is incorrect.
[Info - 11:55:58 AM] Connection to server got closed. Server will restart.
[Info - 11:55:59 AM] Pylance language server 2021.3.4 (pyright ba71f257) starting
[Info - 11:55:59 AM] Server root directory: c:\Users\Owner.vscode\extensions\ms-python.vscode-pylance-2021.3.4\dist
AssignProcessToJobObject: (87) The parameter is incorrect.
[Info - 11:55:59 AM] Connection to server got closed. Server will restart.
[Info - 11:55:59 AM] Pylance language server 2021.3.4 (pyright ba71f257) starting
[Info - 11:55:59 AM] Server root directory: c:\Users\Owner.vscode\extensions\ms-python.vscode-pylance-2021.3.4\dist
AssignProcessToJobObject: (87) The parameter is incorrect.
[Error - 11:56:00 AM] Connection to server got closed. Server will not be restarted.
Python Output:
Error 2021-04-03 11:55:56: Failed to get interpreter information for 'C:\Users\Owner\AppData\Local\Microsoft\WindowsApps\python3.exe' Error: Command failed: "C:\Users\Owner\AppData\Local\Microsoft\WindowsApps\python3.exe" "c:\Users\Owner.vscode\extensions\ms-python.python-2021.3.680753044\pythonFiles\pyvsc-run-isolated.py" "c:\Users\Owner.vscode\extensions\ms-python.python-2021.3.680753044\pythonFiles\interpreterInfo.py"
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.
killed: false,
code: 9009,
signal: null,
cmd: '"C:\\Users\Owner\AppData\Local\Microsoft\WindowsApps\python3.exe" "c:\Users\Owner\.vscode\extensions\ms-python.python-2021.3.680753044\pythonFiles\pyvsc-run-isolated.py" "c:\Users\Owner\.vscode\extensions\ms-python.python-2021.3.680753044\pythonFiles\interpreterInfo.py"'
}
Jupyter Output:
User belongs to experiment group 'pythonJoinMailingListVar3'
User belongs to experiment group 'pythonJediLSP'
User belongs to experiment group 'jupyterTestcf'
User belongs to experiment group 'pythonFindInterpretercf'
Info 2021-04-03 11:55:55: ZMQ install verified.
Info 2021-04-03 11:55:55: id is 8ca66fba-0548-47cb-be1d-90d49ad6965a
Info 2021-04-03 11:55:55: Found existing keyfile at c:\Users\Owner\AppData\Roaming\Code\User\globalStorage\ms-toolsai.jupyter\nbsecret
First Issue, didnt think these applied to me.
I believe these are commented out instructions. I didn't think these applied to me. Opening command pallet to run an issue from with in vs-code wasn't an option. It didn't show up as an available command in the command pallet.
Code Snippet / Additional information
This is a very basic flask app for learning purposes, Code Snippets are probably not relevant.
The text was updated successfully, but these errors were encountered: