-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Debugger stops working in the middle of a debug session #11101
Comments
One more thing I noticed, the languageServerVersion in package.json is 0.5.30, while the language server version installed on my machine is 0.5.45. The same version keeps getting installed when I delete it from local drive. |
Likely microsoft/debugpy#108 |
Thanks @karthiknadig , that is helpful. To add from my side, the problem started occurring a few days (weeks?) back. "python.experiments.enabled": false Have not had the problem since, but was not sure it was this setting or just randomness since I had turned off a few other things and it was only a few hours. Will report back again in a couple of days. |
I am quite sure I am past the problem for my local debugging needs. The workaround in my case was turning off the A/B tests setting for the time being. |
Yep, all symptoms indicate it's the same thing. |
Environment data
"python.jediEnabled"
set to; more info How to update the language server to the latest stable version #3977): Language Serverpython.languageServer
setting: MicrosoftExpected behaviour
Debugging Celery task code which runs within a Django web server process. The celery task_always_eager flag is set, so the code still runs in Django (not in separate Celery process).
Debugger should not stop working during a debug session.
Actual behaviour
Occasionally, but frequently enough, the debugger stops working after stepping through a few steps. The debugger step/continue/run buttons are all enabled, but clicking on them or using shortcuts has no effect, the debugger seems to be stuck on a line of code. The behavior does not seem to have any pattern I can perceive. It occurs at different points on different occasions. Usually when the problem starts, it seems to occur more frequently till I restart VS code, though I am not sure about this.
The + plus to add breakpoints in the watch dropdown of debug tab gets disabled when this condition occurs.
I keep the Raised Exceptions and Uncaught Exceptions checkboxes are unchecked.
This problem re-occurred when I removed all other extensions.
My launch.json is:
The other log which may be of interest is Output -> log (window). I am not sure if this time coincides with when the particular instance of the problem occurred, but it was at least within a couple of minutes:
Steps to reproduce:
I am not able to create a minimal repro of this. It happens while debugging the project and is not predictable. Let me know if there is anything I can try or generate on my side, which could be helpful.
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
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)The text was updated successfully, but these errors were encountered: