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.

Sign up for GitHub

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

Jump to bottom

Integrated terminal gets unresponsive after some usage #49560

Closed
sekogan opened this issue May 9, 2018 · 2 comments
Closed

Integrated terminal gets unresponsive after some usage #49560

sekogan opened this issue May 9, 2018 · 2 comments
Assignees
@Tyriar
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label

Comments

@sekogan
Copy link

sekogan commented May 9, 2018

Steps to Reproduce:

  1. Start VS Code, open the integrated terminal and run a program producing ~80 lines of output. Run that program again 4-5 times.
  2. Scroll the integrated terminal's window back and forth.

VS Code gets unresponsive for 5-20 seconds. The task manager shows huge spikes in CPU and memory usage:

vscode_hang

Tried to run VS Code with --ignore-gpu-blacklist as suggested in #48193 but it didn't help.

ETW traces of the issue: https://1drv.ms/u/s!Avfdd6lsYwdUgrAzPJpI012h9EkEmA

Does this issue occur when all extensions are disabled?: Yes

  • VSCode Version:
    Version 1.23.0
    Commit 7c7da59
    Date 2018-05-03T16:44:55.614Z
    Shell 1.7.12
    Renderer 58.0.3029.110
    Node 7.9.0
    Architecture x64

  • OS Version: Windows 10 x64 1803

  • Graphics: 3840x2160, Intel HD 630 + NVIDIA GTX 1050
@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label May 9, 2018
@sekogan
Copy link
Author

sekogan commented May 10, 2018

Cannot reproduce the issue when VS Code is launched with --disable-gpu.

@Tyriar
Copy link
Member

Tyriar commented May 11, 2018

Duplicate #46954

@Tyriar Tyriar closed this as completed May 11, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label May 11, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Tyriar Tyriar

Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sekogan @Tyriar