Repository navigation
Debug adapter crashes when restarting a debugged test #558
Description
Environment data
VS Code version: 1.19.1
Python Extension version: 0.9.1
Python Version: 3.6.2
OS and version: Windows 10 1709
Actual behavior
Debug adapter crashes.
Expected behavior
Test should restart.
Steps to reproduce:
- Configure the
pytesttest framework - Debug a test of your choice
- Click the restart button
Logs
Output from Python output panel
N/A
Output from Console window (Help->Developer Tools menu)
[Extension Host] debugger listening on port 9333
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2569 [Extension Host] debugger inspector at %cDebugger listening on port 9333.
Warning: This is an experimental feature and could change at any time.
To start debugging, open the following URL in Chrome:
chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9333/0448c037-7731-4c33-bb65-85e967f94138
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:249 [Extension Host] (node:7660) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
t.log @ /C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:249
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:249 [Extension Host] ApplicationInsights:Sender Array(1)
t.log @ /C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:249
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:249 [Extension Host] activating extension
messageService.ts:126 Debug adapter process has terminated unexpectedly
Activity
DonJayamanne commentedon May 10, 2018
Deleted user (@ghost)
I'm unable to replicate this issue at my end.
Its possible this was fixed in the previous release, as we had identified and resolved a number of issues in this space.
no-response commentedon Jun 11, 2018
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.