Frame and variables are not available in debugger window.

For the variables to be available the debug session must be stopped at the breakpoint. Please check Debugging.

I have exactly the same issue and posted this to Stack Overflow here : https://stackoverflow.com/questions/64283701/intellij-debugger-screens-blank

This is the save for every .java I work with and wherever I put the break point. I just get nothing out on the debug menus.

@Jon Can you share the video of what you are doing?

Hi, sure you should be able to see it here : https://www.dropbox.com/s/8tnhuh16afz0scz/Intelij_debug_201012.mp4?dl=0

@Jon, as I see from your comment (https://stackoverflow.com/a/64331418/8958060), the problem is fixed?

Petr, yes indeed you are correct. Whilst I don't know what was the root issue certainly clearing down all the source files and re-applying the one I was using seems to have worked. Thanks for checking back.

Can any one please share that video? I am also facing the same problem with debugging @jon

Its showing Frames are not available.

Hello

I had the same problem and wanted to share my solution here - in case someone can be helped by my fix.

In File | Settings | Build, Execution, Deployment | Toolchains 

Check the Debugger field. For me it was set to 'Bundled GDB'. When I changed it to 'Bundled LLDB', the problem was fixed and now my frames and variables are visible.

(I run CLion on Linux)

Hi, i have the same error but it connecting to server and frame are not available.

I work on windows 10

have you a solution

thanks

H Olfa H

Please send additional information to Help | Contact Support:

• Screenshot of your project structure expanded to the file in which you place a breakpoint
• Screenshot of the breakpoint visible in the editor when it is hit in the Debugger
• Screenshot of the corresponding Run/Debug Configuration settings -> Run | Edit Configurations menu
• The entire idea.log file collected after reproducing the problem -> Help | Show Log in...

Hi, I have the same issue with react application.
I use webstorm.
Debugger does not show the variables and ignored any breakpoint.
Anyone does know how to fix it?

Lendoo73 
Could you try some general troubleshooting steps:

• File > Invalidate Caches.. > enable Clear file system cache and Local History option > Invalidate and Restart
• Close IDE, delete .idea folder and any *.iml files in your project root folder in file explorer, and re-import the project from existing sources
• Close IDE, delete the IDE system directory

If the issue persists, please restart IDE, reproduce the issue again and upload your IDE logs (Help > Collect Logs and Diagnostic Data) here: https://uploads.jetbrains.com, just provide the uploaded file ID. Thanks.

Hi Ivan,

I uploaded the log file,  here is the ID: 2023_09_11_JR6RhXnUxieWHP18744YAj
 

Lendoo73 

In you screenshots, I can see that you have started the app with npm start by choosing this NPM run configuration and hitting Debug. This is not the right way to debug applications that run in browser. To attach a debugger to your web page, you need using the JavaScript Debug run configuration with your app URL

Please refer to https://www.jetbrains.com/help/idea/react.html#react_running_and_debugging_debug for instructions: basically you need to start your application by running npm start (either in terminal or with NPM run configuration), and, once the application is up and running, select the JavaScript Debug run configuration (typically the URL is http://localhost:3000/ but it can be different in your setup - this has to be the URL you normally use to access your application in browser) and press Debug

Six years after this thread has started, I have the same problem is Goland. The uploaded log file is: 

Upload id: 2026_02_11_2BUrfnMkQEPM8Mf2LVotPG (file: goland-logs-20260211-223323420145513916151142.zip)

Is there any chance for this bug to be fixed, please?

The version in which I experienced the bug (2024.*) was newer than the messages from 2023 here abover saying it has been fixed, so I assumed the bug re-appeared. 

But indeed, the new 2025.3.2 already works fine. Thank you.