Skip to content

Python debugging Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor. #816

Closed as not planned

Description

@LittleBen42

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version:
    Version: 1.100.1 (user setup)
    Commit: 91fa95bccb027ece6a968589bb1d662fa9c8e170
    Date: 2025-05-09T15:43:50.040Z
    Electron: 34.5.1
    ElectronBuildId: 11369351
    Chromium: 132.0.6834.210
    Node.js: 20.19.0
    V8: 13.2.152.41-electron.0
    OS: Windows_NT x64 10.0.22631

Steps to Reproduce:

I have an issue with debugging my Python application since few type.

I'm using Python Debugger and I have the following output on the debug console:

Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor.

The debugger hangs and there is no possibility to break the execution.

Only CTRL+C in the debug console is working to exit this debug sesssion

Image

Line 987 is the first breakpoint in my application.

Activity

  1. eleanorjboyd commented on May 21, 2025

    @eleanorjboyd
    Member

    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?

  2. LittleBen42 commented on May 22, 2025

    @LittleBen42
    Author

    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

  3. eleanorjboyd commented on May 27, 2025

    @eleanorjboyd
    Member

    Thanks for the update! Feel free to re-open in the future if you see it again!

  4. LittleBen42 commented on Jul 2, 2025

    @LittleBen42
    Author

    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

    import pandas
    import sys
    
    def main():
        print(sys.argv[1])
        excel = pandas.read_excel(sys.argv[1])
        print(excel)
        return
    
    
    
    if __name__ == "__main__":
        main()
    

    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)

  5. eleanorjboyd commented on Jul 2, 2025

    @eleanorjboyd
    Member

    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.

  6. LittleBen42 commented on Jul 3, 2025

    @LittleBen42
    Author

    Hi Eleanor Boyd (@eleanorjboyd)

    here is my launch.json

    {
        // 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 Debugger: Current File with Arguments",
                "type": "debugpy",
                "request": "launch",
                "program": "${file}",
                "console": "integratedTerminal",
                "args": "${command:pickArgs}"
            },
            {
                "name": "Python Debugger: Current File",
                "type": "debugpy",
                "request": "launch",
                "program": "${file}",
                "console": "integratedTerminal"
            }
        ]
    }
    

    I'm using this python extension ms-python.debugpy-2025.8.0-win32-x64

    Thanks,

    Benjamin

  7. LittleBen42 commented on Jul 4, 2025

    @LittleBen42
    Author

    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

  8. GuGuLianyan commented on Jul 12, 2025

    @GuGuLianyan

    Hello,

    I have got the same problem, And I can not solve it. Did you have got the real reason for it?

    Thank You

  9. GuGuLianyan commented on Jul 12, 2025

    @GuGuLianyan

    Hello,

    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

  10. vs-code-engineering commented on Sep 30, 2025

    @vs-code-engineering

    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.

  11. ChrisIdema commented on Oct 3, 2025

    @ChrisIdema

    I have the same issue with STM32CubeIDE for Visual Studio Code pre-release 3.6.3. It caused the same error.

  12. JDESTM commented on Oct 7, 2025

    @JDESTM

    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.

  13. Garcia6l20 commented on Oct 13, 2025

    @Garcia6l20

    For those how are also facing this issue recently: uninstall STM32CubeIDE extension !

  14. NickSebClark commented on Oct 16, 2025

    @NickSebClark

    I've just found this post after struggling - I too have the STM32CubeIDE extension installed!

  15. ChrisIdema commented on Oct 20, 2025

    @ChrisIdema

    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.

  16. eleanorjboyd commented on Oct 30, 2025

    @eleanorjboyd
    Member

    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.

  17. JDESTM commented on Nov 24, 2025

    @JDESTM

    Fyi a new version of the STM32Cube Debug Core extension including a fix for this issue has been deployed on the Marketplace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

info-neededIssue requires more information from postertriage-neededNeeds assignment to the proper sub-team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions