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

Debugger Performance with Large Goroutine Counts

GoLand integrates with the Delve debugger to provide a dedicated Goroutines view for tracking concurrent execution paths. While this allows for detailed memory inspection and stack trace navigation, the interface must handle the state of potentially thousands of active goroutines simultaneously.

In applications with high concurrency, the volume of data transmitted from the Delve backend to the IDE can impact the responsiveness of the user interface. There is a technical trade-off between providing a complete real-time snapshot of all goroutines and maintaining UI fluidity during a breakpoint hit.

What are the current limits for the number of goroutines the UI can render before significant lag occurs? Is there a configuration to paginate or filter the Goroutines view to improve accessibility in large-scale concurrent applications?