-
Notifications
You must be signed in to change notification settings - Fork 510
Debug adapter process has terminated unexpectedly (read error) #1579
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
Comments
@PrzemyslawKlys, the logs you've uploaded there only have the vscode log, no EditorServices log. I'm suspecting that this is a duplicate of #1441 though. |
When I attach zip it's usually what is there with logs. This must mean EditorServices.log was not created :/ |
I also experience this error from time to time - it hits randomly, but getting worse after upgrade to v1.10.0 and v1.10.1 this morning. I have attached my EditorServices.log The error occurs often when I debug and using step with F10. If I do it too rapidly, the error occurs even more often. |
I updated to the latest version of the PowerShell extension 1.12.0 released March 29, 2019. Since then I have been unable to use the debugger at all. Prior to this release I noticed that a PowerShell command prompt would open when I opened a PowerShell script file. If I closed the command prompt it would prompt me and ask if I wanted to start a new one. None of that is happening now with this new version. Update |
System Details
System Details Output
Issue Description
I am experiencing a problem with... not able to run code
Happens randomly, happens more with newest release 1.9.0, haven't seen (read error) in older versions. But it also can be related to WIndows 10 1809 or OneDrive (I do keep my files on one drive - double security - i've many times were able to save uncommited code that I've deleted just by using onedrive).
Expected Behaviour
Not crashing.
Actual Behaviour
Crashing, usually have to restart PowerShell for it to work again. F5 stops responding. Sometimes starts responding without restart.
Attached Logs
1539415847-32d7f941-f01e-4f22-8529-d050803302021539415844201.zip
The text was updated successfully, but these errors were encountered: