Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excessive Debugger Console output causes VS Code to become unresponsive #95981

Closed
baulig opened this issue Apr 23, 2020 · 1 comment
Closed
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)

Comments

@baulig
Copy link

baulig commented Apr 23, 2020

Issue Type: Performance Issue

When debugging an app that dumps excessive amounts of output to the Debugger Console, VS Code becomes unresponsive.

In my example, I was debugging a .NET Core app and by accident logged some 15 MB of debugging output to the console - about 11k lines some of which were extremely long because it included a base64-encoded binary. This was a mistake but due to the unresponsiveness it was hard to find which piece of my code was actually doing that.

This is probably not a scenario that will happen during day-to-day usage, but I think we should still deal with it in a reasonable way.

VS Code version: Code - Insiders 1.45.0-insider (d342048, 2020-04-23T07:46:52.128Z)
OS version: Darwin x64 19.4.0

@isidorn
Copy link
Contributor

isidorn commented Apr 24, 2020

Thanks for reporting this, however dup of #81464

@isidorn isidorn closed this as completed Apr 24, 2020
@isidorn isidorn added *duplicate Issue identified as a duplicate of another issue(s) debug Debug viewlet, configurations, breakpoints, adapter issues labels Apr 24, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Jun 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants