Crash on extensive output in debug console
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java, typescript, vscode
- Domain
- devtools, testing-qa
Research direction
Reproduce the crash using the provided JUnit 5 CrashTest and compare it with the throttled noCrashTest in the debug console. Start from the debug-console output path, then verify that running the million-line test no longer crashes VS Code while output remains usable.
Written by the indexing model from the issue text.
Description
Flooding std-out in debug console by a JUnit test in a short amount of time seems to result in total vscode crash.
Running the given the following simple JUnit 5 "Test" results in crash:
import org.junit.jupiter.api.Test;
public class CrashTest {
@Test
public void crashTest() {
for (int i = 0; i < 1_000_000; i++) {
System.out.println((i + 1));
}
}
}
When releasing the output pressure with the example below, debug console can keep up and there is no crash.
@Test
public void noCrashTest() throws InterruptedException {
for (int i = 0; i < 1_000_000; i++) {
if (i % 1000 == 0)
Thread.sleep(500);
System.out.println((i + 1));
}
}
Environment
- Operating System: Ubuntu 22.04
- JDK version: 17.0.7
- Visual Studio Code version: 1.79.2
- Java extension version: v1.19.0
- Debugger for Java version: v0.51.0
- Test Runner for Java version: v0.39.0
Steps To Reproduce
- Run the test
- Crash
- Dominant language
- TypeScript
- Stars
- 591
- Forks
- 429
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 19
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-java-debug
-
ai-triaged enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoft/vscode-java-debug#1689 · 2 comments ·
-
ai-triaged bug
microsoft/vscode-java-debug#1666 · 1 comment · 1 assignee ·
-
ai-triaged bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoft/vscode-java-debug#1658 · 1 comment ·
-
ai-triaged enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/vscode-java-debug#1628 · 3 comments ·
-
Feature support. Openai-triaged enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/vscode-java-debug#1616 · 1 comment ·
All issues in microsoft/vscode-java-debug
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·