take a long time to continue debugging after halt at a breakpoint

[DonJayamanne]

From @aeschli on March 30, 2017 7:52

From @Liudx1985 on March 30, 2017 1:12

• VSCode Version: Code 1.10.2 (8076a19fdcab7e1fc1707952d652f0bb6c6db331, 2017-03-08T14:02:52.799Z)
• OS Version: Windows_NT ia32 6.1.7601
• Extensions:

Extension	Author	Version
python	donjayamanne	0.6.0
xml	DotJoshJohnson	1.7.0
code-runner	formulahendry	0.6.15
changeEncode	lanmj2004	0.0.8
cpptools	ms-vscode	0.10.5
sublime-keybindings	ms-vscode	2.0.1

---

Steps to Reproduce:

1.set debug point at python code,start debugging
2.halt at breakpoint, check the variables a little while, then continue run, the vscode takes a very long time to work normal

Copied from original issue: microsoft/vscode#23631

Copied from original issue: DonJayamanne/pythonVSCode#854

[DonJayamanne]

From @asierralozano on April 20, 2017 13:53

I'm having this issue too. Just to clarify, i'm using the remote debugging for debugging Autodesk Maya

[DonJayamanne]

@asierralozano , apologies for not getting back to you on this issue.
The PTVS team are in the process of making some changes to the debugger that would improve the performance of this.
FYI - the extension is making use of the debugger developed by the PTVS team.

[ghost]

@brettcannon There are two solutions to this problem:

1. Rewrite the PTVS debugger in Cython (actually not as difficult as it seems)
2. Switch to the pydevd debugger.

I have an uncompleted PR for the latter. Will submit if asked, but I don't have time to complete it.

[brettcannon]

@xoviat thanks for the suggestions. We are actively discussing this already on the team and how we can share the work with the PTVS team.

[theotheo]

Are there any changes?

[DonJayamanne]

Please check here:
#538

[DonJayamanne]

@ghost @theotheo @asierralozano
Hi everyone, you may or may not be aware of this, we've started working on a new debugger for the python extension. It is still labeled as experimental. However it is shipped with the extension.

Please could you try this new debugger and let us know how it is.

• You could either chose the Python Experimental debug configuration
• Or update the "type":"python" setting in launch.json to "type":"pythonExperimental" to try this new debugger.

[no-response]

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.

[ivmarkp]

Can confirm, experimental debugger is MUCH faster on Windows 7. excel = pd.ExcelFile(FILE) operation used to take around 2 minutes for a file of size 5-6 MB but this time has reduced to as much as only 10-12 seconds with experimental debugger.