Server[pid=37672] is already being debugged

[CybranM]

Hello! This addon is amazing but Ive been running into this issue recently:

Ive never run into this issue until last week where it now happens every time I start debugging Blender.

Visual Studio Code about:
Version: 1.96.4 (system setup)
Commit: cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba
Date: 2025-01-16T00:16:19.038Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

[dpshamonin]

Hello,

I’ve been using this add-on for about a year across different Blender versions on Windows 10. Have never encountered this pop-up before. However, after the latest Visual Studio Code update, it suddenly appeared.

Version: 1.97.0 (system setup)
Commit: 33fc5a94a3f99ebe7087e8fe79fbe1d37a251016
Date: 2025-02-04T22:41:26.688Z
Electron: 32.2.7
ElectronBuildId: 10660205
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

[Patochun]

Hello, same issue for me. Suddenly appeared after last Visual Studio Code update. The button Open 'launch.json' open nothing.

[3DMage]

I have recently started seeing this pop-up as well. I even downgraded VSCode to version 1.95.3 and I am still getting the pop-up.
I have also tested this using versions 0.23 - 0.25 of the Blender Development Add-On using both Python 3.12 and Python 3.13, and am still getting the pop-up.

The pop-up does seem to stop if I have at least one instance of Blender running that was opened via VSCode, and I open another instance of Blender through VSCode, though that is not ideal.

I should also mention this has been occurring for Blender 4.0, 4.1, 4.2, and 4.3.

Version: 1.95.3 (user setup)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

[3DMage]

UPDATE: I downgraded the Python Debugger extension to v2024.14.0 and that removed the pop-up issue. Note I am also using version 1.95.3 of VSCode. Not sure if this makes a difference. Would be interested to know.

Version: 1.95.3 (user setup)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

[Patochun]

Ok, I just downgrade Python Debugger as you did and the pop-up issue gone.

[windowslucker1121]

I had the same issue and downgrading the Python Debugger fixed it, thanks for pointing that out!

[iplai]

UPDATE: I downgraded the Python Debugger extension to v2024.14.0 and that removed the pop-up issue. Note I am also using version 1.95.3 of VSCode. Not sure if this makes a difference. Would be interested to know.

Version: 1.95.3 (user setup) Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813 Date: 2024-11-13T14:50:04.152Z Electron: 32.2.1 ElectronBuildId: 10427718 Chromium: 128.0.6613.186 Node.js: 20.18.0 V8: 12.8.374.38-electron.0 OS: Windows_NT x64 10.0.19045

Click the down arrow behind uninstall button and select a version lower than v2024.14.0, then the pop-up issue gone.

[CybranM]

Downgrading Python Debugger to v2024.14.0 removed the popup (after restarting VSCode)
Im using VSCode 1.97.1

This is a temporary fix though, Im curious if this is something that should be fixed in the extension or if its on VSCode to fix.
I dont have any ability to know or fix it myself

[IPv6]

Same error here, on Windows 10 (no such problem on MacOs, for example).
Deinstalled Python Debugger extension and everything fine now :)

Log-Centered Debugging FTW!! :)

[anclude-dev]

Downgrading Python Debugger worked for me, thanks! I spent so much time trying to figure this out...

[theoryshaw]

the downgrading worked for awhile, but now i get...

Unfortunately upgrading and/or downgrading, doesn't seem to work anymore.
Anyone else have this problem?

[Mateusz-Grzelinski]

Hi, I am just reviewing issues, should we treat this issue the same as #218 ? From what I read the fix is the same in both cases?