You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Python debugging Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor. #816
hm very interesting it is coming from the bundled part of the debugger extension. Can you try uninstalled and reinstalling the python debugger repo? Also what version of python are you using?
I don't see the issue anymore.
I was using Python 3.10.4 and I have updated to Python 3.13.3, I have updated my venv to the new Python 3.13.3 and re install all my dependencies packages.
I have mentioned that the issue was present with all extension disabled but I have forget to restart vscode, therefore I need at least the Python extension.
I have regenerated the venv with the python extension and looks like there was a missing dependencies in the pandas package.
I'm now using the default Python Debugger (I no longer have a launch.json) and I don't have the issue anymore.
I have installed Python 3.13.5 which is now configuring the path with the Launch directory with py.exe instead of usual python.exe.
When I have the issue initially, I have change my PATH to point on the Python3.13 directory which hold the python.exe
WIth this setup, I have the issue.
I have reverted back to the standard config (with Launch directory) and I have regenerated the venv and now everything is working as previously.
I have got the same problem, And I can not solve it. Did you have got the real reason for it?
Thank You
I Have Resoled It. There are some conflict between STM32-Plugs and other debug feature. I have little remember that STM32-Debug-Plugs have some warning info when I start use it. You may should check that is there any other debug-plugs will change debug feature
Reacted by Lincoln Lorenz, Chris Idema and Fredrik Karlsson
Chris Idema (@ChrisIdema), GuGuLianyan, the issue was indeed located on STM32Cube Debug extension side, a fix will be delivered with next version. Apologize for the inconvenience.
closing as it is the extension causing the issue- thanks!
@ChrisIdema, @GuGuLianyan, the issue was indeed located on STM32Cube Debug extension side, a fix will be delivered with next version. Apologize for the inconvenience.
Activity
eleanorjboyd commentedon May 21, 2025
hm very interesting it is coming from the bundled part of the debugger extension. Can you try uninstalled and reinstalling the python debugger repo? Also what version of python are you using?
LittleBen42 commentedon May 22, 2025
Hi Eleanor Boyd (@eleanorjboyd),
I don't see the issue anymore.
I was using Python 3.10.4 and I have updated to Python 3.13.3, I have updated my venv to the new Python 3.13.3 and re install all my dependencies packages.
I have mentioned that the issue was present with all extension disabled but I have forget to restart vscode, therefore I need at least the Python extension.
Best Regards,
Benjamin
eleanorjboyd commentedon May 27, 2025
Thanks for the update! Feel free to re-open in the future if you see it again!
LittleBen42 commentedon Jul 2, 2025
Hi Eleanor Boyd (@eleanorjboyd) ,
I have changed my PC this week and I'm facing the error again.
For my old project, I have regenerated the venv and everything is fine so far.
I have started a new project and created a venv with the python extension from vscode. I have install pandas package and I'm using a very simple code
and when I start the debugger I have the error again
Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor.the debugger is launched with the following commands :
x:; cd '<work_dir>'; & '<work_dir>\.venv\Scripts\python.exe' 'c:\Users\<me>\.vscode\extensions\ms-python.debugpy-2025.8.0-win32-x64\bundled\libs\debugpy\launcher' '56250' '--' '<work_dir>\perso_parser.py'So far didn't manage to solve it.
I'm using Python 3.13.5 on this new setup and vscode 1.101.2 (user setup)
eleanorjboyd commentedon Jul 2, 2025
Hi! Can you send over your launch.json you are running? The error suggests you are using the legacy debugger and not the recent debugpy.
LittleBen42 commentedon Jul 3, 2025
Hi Eleanor Boyd (@eleanorjboyd)
here is my launch.json
I'm using this python extension
ms-python.debugpy-2025.8.0-win32-x64Thanks,
Benjamin
LittleBen42 commentedon Jul 4, 2025
Hi Eleanor Boyd (@eleanorjboyd) ,
I have regenerated the venv with the python extension and looks like there was a missing dependencies in the pandas package.
I'm now using the default Python Debugger (I no longer have a launch.json) and I don't have the issue anymore.
I have installed Python 3.13.5 which is now configuring the path with the Launch directory with py.exe instead of usual python.exe.
When I have the issue initially, I have change my PATH to point on the Python3.13 directory which hold the python.exe
WIth this setup, I have the issue.
I have reverted back to the standard config (with Launch directory) and I have regenerated the venv and now everything is working as previously.
Best Regards,
Benjamin
GuGuLianyan commentedon Jul 12, 2025
Hello,
I have got the same problem, And I can not solve it. Did you have got the real reason for it?
Thank You
GuGuLianyan commentedon Jul 12, 2025
I Have Resoled It. There are some conflict between STM32-Plugs and other debug feature. I have little remember that STM32-Debug-Plugs have some warning info when I start use it. You may should check that is there any other debug-plugs will change debug feature
vs-code-engineering commentedon Sep 30, 2025
Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.
LittleBen42, you can help us out by closing this issue if the problem no longer exists, or adding more information.
ChrisIdema commentedon Oct 3, 2025
I have the same issue with STM32CubeIDE for Visual Studio Code pre-release 3.6.3. It caused the same error.
JDESTM commentedon Oct 7, 2025
Chris Idema (@ChrisIdema), GuGuLianyan, the issue was indeed located on STM32Cube Debug extension side, a fix will be delivered with next version. Apologize for the inconvenience.
Garcia6l20 commentedon Oct 13, 2025
For those how are also facing this issue recently: uninstall STM32CubeIDE extension !
NickSebClark commentedon Oct 16, 2025
I've just found this post after struggling - I too have the STM32CubeIDE extension installed!
ChrisIdema commentedon Oct 20, 2025
A workaround is to use VS Code profiles: https://code.visualstudio.com/docs/configure/profiles
Restart VS Code after uninstalling STM32CubeIDE extension or it will show up twice.
eleanorjboyd commentedon Oct 30, 2025
closing as it is the extension causing the issue- thanks!
JDESTM commentedon Nov 24, 2025
Fyi a new version of the
STM32Cube Debug Coreextension including a fix for this issue has been deployed on the Marketplace.