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

High memory usage on local machine when flushing a large number of characters to screen #112759

Closed
Bobholamovic opened this issue Dec 1, 2020 · 6 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues
Milestone

Comments

@Bobholamovic
Copy link

Issue Type: Performance Issue

Just one step to reproduce it:

base64 /dev/urandom

And you'll see the memory usage of VSCode on the local machine surges, until the program stops working.

Does this have anything to do with a local screen buffer?

Extension version: 0.56.0
VS Code version: Code 1.51.1 (e5a624b, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363
Remote OS version: Linux x64 4.15.0-74-generic

@roblourens
Copy link
Member

Does this sound like anything that we might have an issue for @meganrogge?

I guess I would expect

And you'll see the memory usage of VSCode on the local machine surges

to some extent, but not

until the program stops working.

@meganrogge
Copy link
Contributor

I haven't seen anything similar. Can confirm it only happens for remote windows.

@Bobholamovic
Copy link
Author

@roblourens Well, what I meant was that the program would stop working because of the OOM error. But shouldn't we expect the resources of the remote server to be heavily consumed instead of the local machine, since the program is actually running on the remote server?

@roblourens
Copy link
Member

It will use some memory on the local side, partly for the screen buffer but partly just from lots of allocations in JS that don't get garbage collected right away. Should not be leaky though.

@roblourens roblourens transferred this issue from microsoft/vscode-remote-release Dec 17, 2020
@roblourens roblourens added bug Issue identified by VS Code Team member as probable bug terminal Integrated terminal issues labels Dec 17, 2020
@meganrogge meganrogge added this to the Backlog milestone Dec 17, 2020
@meganrogge
Copy link
Contributor

Duplicate of #111562

@meganrogge meganrogge marked this as a duplicate of #111562 Dec 17, 2020
@meganrogge meganrogge added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 17, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Jan 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues
Projects
None yet
Development

No branches or pull requests

4 participants
@roblourens @Bobholamovic @meganrogge and others