Skip to main content
Visitor II
July 30, 2025
Solved

Error while debugging other python projects

  • July 30, 2025
  • 5 replies
  • 1203 views

I get a Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor. error while debugging other python projects. This issue gets resolved when I disable the STM32Cub for Visual Studio Code Core extension and its related extensions.

To reproduce: 

Open an existing python project or package (workspace)

Launch the debug session. 

It tries to start the session and in a few seconds throws this error and stops the debugger.

Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor.

Please see https://github.com/microsoft/vscode/issues/249341#issuecomment-3064965337

 

    This topic has been closed for replies.
    Best answer by Nawres GHARBI

    Hi @Burrr 

    we are currently working on a fix for this issue and this will be delivered next release (November) or later on, will depend on validation findings

    please do not hesitate to contact me for further details

    #ticket: T1IDE-2888

    5 replies

    Graduate II
    July 31, 2025

    Maybe good practice is to rely on VSCode's profiles what are promoting some isolation kind: https://code.visualstudio.com/docs/configure/profiles

    Technical Moderator
    October 7, 2025

    Hi @Burrr 

    we are currently working on a fix for this issue and this will be delivered next release (November) or later on, will depend on validation findings

    please do not hesitate to contact me for further details

    #ticket: T1IDE-2888

    Explorer
    November 7, 2025

    Hi @Nawres GHARBI ,

     

    We have the same problem here.

    Can we have an update on the solution ?

    Or maybe a link to the issue feed?

     

    Thanks,

    Arnaud

    Super User
    November 7, 2025

    @ArnaudC wrote:

    Or maybe a link to the issue feed?


    Sadly, the ST ticketing system is internal and not visible to customers.

    Usually, ST people make this clear when referring to internal tickets; eg, here.

    @Nawres GHARBI 

    Technical Moderator
    November 10, 2025

    Hello the fix is already implemented and will be in the coming release end of W47

    ST Employee
    November 25, 2025

    @Burrr @Andrew Neil @ArnaudC @Cartu38 OpenDev 

    Please be aware that the issue has been fixed and the extension update is now available.

    vincent_grenet_0-1764052436754.png