Degraded performance when using breakpoints

[evan-kochuk-niche]

Degraded performance when using breakpoints

[hyangah]

@evan-kochuk-niche Do you remember the go version and the delve version you used before and now?

Delve v1.22.1 (Go debugger) was released last week. If you install the previous version, do you see any difference?

go install github.com/go-delve/delve/cmd/[email protected]

The unit tests on my production code takes even longer, on the order of minutes, also on variable assignment.

Do you mean that unit tests in debugging mode?
Is it fast when you use the command line tool for debugging? dlv debug

[evan-kochuk-niche]

@evan-kochuk-niche Do you remember the go version and the delve version you used before and now?

I have not updated my go version from 1.21 in months. Delve is just set to use @latest

Delve v1.22.1 (Go debugger) was released last week. If you install the previous version, do you see any difference?

Gave it a shot; I do not.

The unit tests on my production code takes even longer, on the order of minutes, also on variable assignment.

Do you mean that unit tests in debugging mode? Is it fast when you use the command line tool for debugging? dlv debug

Yes, in debugging mode (as per clicking "Debug test" above the function in the screenshot). This is only an issue when a breakpoint is set. If no breakpoint is set, the test finishes in under a second.

[hyangah]

Can you try dlv debug commandline, to see if it perform this bad?
Last week release carries a change that just disables installation of a helper binary on windows, and that is unrelated to debugging. I don't recall any memorable change in v0.41.0 release either. Is there any OS update or system library update in your windows that may cause a different behavior or introduce extra checks when programs are debugged?

[evan-kochuk-niche]

I have been able to confirm that running dlv debug via commandline has no performance degradation.

Only the golang debugging inside of VS Code is affected (and only then when a breakpoint is hit). And it is only the go debugging -- C# debugging in VS Code is unaffected.

My organization's IT department claims that there were no recent updates pushed out to our machines, but I don't have any details more than that. I'm kinda stumped; never seen anything like this before.

[hyangah]

I don't know if this will show any more info, but how about collecting logs?

    "go.delveConfig": {
        "logOutput": "dap,debug",
        "showLog": true,
    },    

This will cause to print out timestamped log messages in the DEBUG CONSOLE panel.

[evan-kochuk-niche]

I think this can probably be closed.

I experimented with a different IDE entirely -- GoLand -- and am observing the same breakpoint behavior, which makes me think that whatever issues I'm encountering, they are not tied to VS Code, but either Delve or some hardware issue.

[hyangah]

Thanks for the update. Closing.