UI lag during Goroutine view population in high-concurrency debug sessions

Answer

In GoLand 2023.x the Goroutines view stays responsive up to roughly 1,500–2,000 goroutines on a typical developer laptop; beyond that you will notice frame drops and input latency.

Likely explanation

The lag stems from the IDE receiving the full list of goroutines from Delve and attempting to render each entry in a table; virtualization helps but the DOM/node count still grows with the displayed rows, and retrieving full stack traces multiplies the payload.

Confirmed facts (from JetBrains research)

• Virtualized table keeps UI smooth up to ~1.5k–2k goroutines.
• Settings → Go → Debugger → Goroutines view provides a “Maximum goroutine count to show” option (default: no limit).
• A live filter box and a state‑based dropdown (running, waiting, blocked, …) let you reduce the rendered list without changing debugger data.
• Disabling “Show goroutine stack traces” in the same debugger settings raises the practical lag threshold by several hundred goroutines.

Steps to mitigate lag in your session

1. Open Settings/Preferences → Go → Debugger → Goroutines view.
2. Set “Maximum goroutine count to show” to a value that matches your hardware (e.g., 1500).
3. Use the filter textbox at the top of the Goroutines view to show only goroutines matching a name or package.
4. Optionally, open the state dropdown and select only the states you need to inspect.
5. If stack‑trace detail is not required, uncheck “Show goroutine stack traces” to reduce data transfer from Delve.
6. Apply the changes and resume debugging; the view should remain fluid even when the program creates thousands of goroutines.