Remote attach debug server not dying upon killing the attached process

[zbs]

Type: Bug

Behaviour

Extremely frequently the VS Code remote attach debugger will not die when I kill the python -m debugpy ... process that is attaching to the port 5678. Until I restart the IDE I cannot start debugging again, because otherwise it will complain that "Python debugger is already debugging another instance". My colleaques haven experiened this issue as well, and it seems to be a recent regression (last couple of weeks).

As I wrote this, I cannot click the "Create on GitHub" button because VSCode is seeming unresponsive. I resolved by restarting the IDE.

Steps to reproduce:

1. Use the below config for debugger
2. Run python -m debugpy --wait-for-client --listen 5678 /path/to/module.py
3. Run debugger
4. Either detach debugger or CTRL-C the process on command line

Diagnostic data

launch.json configuration

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [

        {
            "name": "Python: Remote Attach",
            "type": "python",
            "request": "attach",
            "connect": {
                "host": "localhost",
                "port": 5678
            },
            "pathMappings": [
                {
                    "localRoot": "${workspaceFolder}",
                    "remoteRoot": "."
                }
            ],
            "justMyCode": false
        }
    ]
}

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Output for Python Debugger in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python Debugger)

XXX

Extension version: 2024.15.2024121301
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 4.18.0-372.32.1.el8_6.x86_64
Remote OS version: Linux x64 4.18.0-372.32.1.el8_6.x86_64
Remote OS version: Linux x64 4.18.0-372.32.1.el8_6.x86_64
Connection to 'SSH: zbs-carp2' could not be established Canceled
Remote OS version: Linux x64 4.18.0-372.32.1.el8_6.x86_64

• Python version (& distribution if applicable, e.g. Anaconda): 3.8.19
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda

System Info

Item	Value
CPUs	11th Gen Intel(R) Core(TM) i9-11950H @ 2.60GHz (16 x 2611)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	63.73GB (37.47GB free)
Process Argv	--folder-uri vscode-remote://ssh-remote%2Bzbs-carp2/physical/gpfs/carp2-home/car_home02/data_files/jcs/zsilversmith/dev/git/eis3 --crash-reporter-id 2a67a766-b9ca-442f-87e6-12fdf4c1e37f
Screen Reader	no
VM	0%

Item	Value
Remote	SSH: zbs-carp2
OS	Linux x64 4.18.0-372.32.1.el8_6.x86_64
CPUs	AMD EPYC 7763 64-Core Processor (128 x 0)
Memory (System)	2014.91GB (1217.89GB free)
VM	0%

Item	Value
Remote	SSH: zbs-carp2
OS	Linux x64 4.18.0-372.32.1.el8_6.x86_64
CPUs	AMD EPYC 7763 64-Core Processor (128 x 0)
Memory (System)	2014.91GB (1217.89GB free)
VM	0%

Item	Value
Remote	SSH: zbs-carp2
OS	Linux x64 4.18.0-372.32.1.el8_6.x86_64
CPUs	AMD EPYC 7763 64-Core Processor (128 x 0)
Memory (System)	2014.91GB (1217.89GB free)
VM	0%

Connection to 'SSH: zbs-carp2' could not be established Canceled

Item	Value
Remote	SSH: zbs-carp2
OS	Linux x64 4.18.0-372.32.1.el8_6.x86_64
CPUs	AMD EPYC 7763 64-Core Processor (128 x 0)
Memory (System)	2014.91GB (1217.89GB free)
VM	0%

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

[karthiknadig]

@zbs In this case is the debugger process (i.e., python -m debugpy) terminated? or is that also blocked.

Moving this to debugpy to investigate. Basically, if the process is terminated, we do an atexit registration that should let IDE know that the debugger is terminated. We need to make sure that the termination message is being sent to the IDE.

If debugpy is terminating correctly after sending the message, then this issue is in the DAP Client, and we should move this issue to VS Code core.

[rchiodo]

I can't seem to reproduce this myself. Can you turn on logging and send back the logs? They'll end up on the remote machine. It should say if the debugger sent the terminate or not.

[zbs]

Thanks all. Running with logging and will report back

@zbs In this case is the debugger process (i.e., python -m debugpy) terminated? or is that also blocked.

Yes AFAICT it's properly killed.

[zbs]

OK repro'd again. This time, steps were

1. python -m debugpy --wait-for-client --listen 5678 --log-to ~/vscode_debug_logs ....
2. Attach via vs code gui
3. Let the debugger break on an exception/breakpoint
4. CTRL-C out of the command line process
5. Re-run step 1
6. Re-run step 2. At this point, the blue "processing/in progress" animation starts and never stops
7. Kill the command line process that is waiting
8. Re-run step 1
9. Attempt to use VS code debug gui once more. This is when I hit a "another instance running" message.

I have the logs, how should I send them, or what should I extract from them?

[rchiodo]

You can just zip them and drop the zip file in the issue.

[rchiodo]

We might need the VS code side logs too, that would be using the logToFile option in the launch.json. It will write out the logs to where the debugger extension is installed.

[zbs]

logs.tar.gz

[rchiodo]

There should have been some pydevd logs too, not sure why those didn't show up. There were four instances of the debugger starting.

Two looked like it was killed by the keyboard interrupt and the client responded with the disconnect. The other two look like it failed to connect.

I'd fix this part first though. You're using a super old debugpy on the server. Not sure how it even works:

I+00000.035: Linux-4.18.0-372.32.1.el8_6.x86_64-x86_64-with-glibc2.10 x86_64
             CPython 3.8.15 (64-bit)
             debugpy 1.0.0b12

Debugpy's latest is 1.8.11

[rchiodo]

You might also use a newer CPython, as that version isn't technically supported anymore.

[zbs]

Ah, that's probably why. I'll ask our internal maintainer of that conda environment to bump the debugpy version. After you pointed that out, I've switched back to our main environment, which has version 1.8, and I have yet to repro this issue.

Since that seems like the strongest lead, we can probably close this out unless I encounter this problem again. Thanks for all the help and sorry for the time waste.