Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

When debug in second time, there is no code prompt in debug console

Open
#1,536 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, vscode
Domain
devtools

Research direction

Start with the attached demo.zip in VS Code and reproduce the documented first-debug and second-debug sequence using the listed Windows, Java, and extension versions. Compare the DEBUG CONSOLE completion behavior between sessions and check whether deleting target changes the result. Done means code prompts remain available after stopping and rerunning the debug session.

Written by the indexing model from the issue text.

Description

ai-triaged bug

Good day all,

When I use vscode to debug java code, I found that when I debug my code more than one time, there is no code prompt in DEBUG CONSOLE.

My Environment:
Windows: Windows 11 Professional 24H2
VSCode: 1.97.2
Debugger for Java: v0.58.1
Java: Java 17

Reproduce Steps:

  1. Open code in VSCode;
  2. Waiting Java compile, and add break point;
  3. First time run code in debug mode;
  4. Open DEBUG CONSOLE, the code prompt function going well.
    Image
  5. Stop debug;
  6. Rerun code in debug mode and open DEBUG CONSOLE, there is no code prompt;
    Image

Continually, the code prompt function keeps unavailable even if:

  • Close and re-open vscode;
  • Clean Work Space
  • Re-compile the project
  • etc.

Unless, code prompt in DEBUG COLSE works again when:

  1. Close VSCode;
  2. Delete target folder in the directory;
  3. Reopen the project and first time debug the code;

The minimalist code is attached (Just a simple Springboot Application). Could anyone check if it is a bug or environment specific?

demo.zip

Dominant language
TypeScript
Stars
591
Forks
429
Avg merge
1d 9h
Merged PRs (30d)
19

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-java-debug

All issues in microsoft/vscode-java-debug

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.