Crash on extensive output in debug console

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

1. Run the test
2. Crash

Riproduci il crash usando il CrashTest JUnit 5 fornito e confrontalo con il noCrashTest limitato nella console di debug. Parti dal percorso di output di debug-console, quindi verifica che l'esecuzione del test da un milione di righe non provochi più il crash di VS Code, mentre l'output rimane utilizzabile.