Failed refactors (due to rope errors) leave zombie processes #2374
Labels
area-editor-*
User-facing catch-all
area-intellisense
LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.
bug
Issue identified by VS Code Team member as probable bug
Uh oh!
There was an error while loading. Please reload this page.
Environment data
Actual behavior
When refactors fail due to rope errors (as has been documented in other issues), the process of a Python call to refactor.py does not exit.
Expected behavior
Failed refactors should have the process exit nicely.
Steps to reproduce:
b
inself.b
fails (stacktrace seen in the output log below).code --status
in the terminal and see that the refactoring process calls did not exit: (PIDs 4077 and 4078)Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)The text was updated successfully, but these errors were encountered: