Run python file in terminal inconsistent (freezes and does weird things when trying to run a python file again)

Environment data

• VS Code version: June 2021 (version 1.58)
• Extension version (available under the Extensions sidebar): 2021.6.944021595 (latest)
• OS and version: Win 10 Latest Update
• Python version (& distribution if applicable, e.g. Anaconda): 3.9.6
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): N/A
• Relevant/affected Python packages and their versions: N/A
• Relevant/affected Python-related VS Code extensions and their versions: Pylance (2021.7.2) , Jupyter (2021.6.999662501)
• Value of the python.languageServer setting: Default

Expected behaviour

Python script runs when clicking the play button/run python in terminal and then you can kill the terminal and run the script again

Actual behaviour

Running a python script with the play button/run python in terminal does run, then when you kill the terminal and run it again that the terminal glitches or something and does not display anything and freezes to the point where pressing the kill terminal button does nothing, you have to close the terminal and then run the code again and then it goes back to normal but if you scroll up you can se like a glitched column of text.

Video of what’s happening: https://user-images.githubusercontent.com/66221090/125100584-e1a3e000-e09e-11eb-92b5-b049d7971e72.mp4

Steps to reproduce:

While this was happening I did some troubleshooting and downgraded vs code to the may update and got fixed(even a total uninstall of vs code and reinstalling latest version does not fix it), so I think this is a bug related to the June update that released earlier today, so I think these are the steps to reproduce:

1. Install latest version of VS code (June 2021 version 1.58)
2. Install the Microsoft python extension
3. Run any python script with the run in terminal function that the python extension includes

[Marines1775]

Could you explain to me how you can close this when its an obvious BUG and has not been fixed?

[karthiknadig]

The code where the issue exists is not in this repository. For issue like this, either we transfer issue if it is new and there is no bug already tracking this in the VS Code repo; Or we close on behalf of an existing issue in VS Code repo. The bug will be addressed by VS Code and fixed in that repo.