Skip to content

wired behavior after sudden stop #1539

@McDaddy

Description

@McDaddy

Describe the bug

I have reproduced this issue in multiple v2 versions.

it is not just happens at debug time, also happens in my prod env

20251112010042_rec_.mp4

To Reproduce

step1.
choose one example file in official repo. e.g. bubbletea/examples/mouse/main.go

step2.
use vscode to debug it. launch.json is like this

···
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Debug Current File",
"type": "go",
"request": "launch",
"mode": "debug",
"program": "${fileDirname}",
"args": [],
"console": "integratedTerminal",
"env": {
"LOG_LEVEL": "debug"
},
"showLog": true,
"trace": "verbose"
}
]
}
···

step3.

click stop debugger button.

then the whole screen runs into a mass.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Image

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions