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

Terminal stops output after random number of characters #46037

Closed
MJJBennett opened this issue Mar 17, 2018 · 2 comments
Closed

Terminal stops output after random number of characters #46037

MJJBennett opened this issue Mar 17, 2018 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@MJJBennett
Copy link

MJJBennett commented Mar 17, 2018

Issue Type: Bug

Simple piece of test code here:

#include <iostream>

int main() {
    for (int i = 0; i < 300; i++) {
        std::cout << i << std::endl;
    }
}

Output's failure may look like this:

1
2
3
[...]
40
41
4

VS Code version: Code 1.21.1 (79b44aa, 2018-03-14T14:46:47.128Z)
OS version: Windows_NT x64 10.0.16299

System Info
Item Value
CPUs AMD Ryzen 7 1700 Eight-Core Processor (16 x 2994)
Memory (System) 15.95GB (9.91GB free)
Process Argv C:\Program Files\Microsoft VS Code\Code.exe
Screen Reader no
VM 0%
Reproduces without extensions: Yes. Please note - I saw that a prior issue with this exact same problem had been closed because it was caused by extension(s) (Issue #43280); in order to avoid that, I uninstalled every extension I had installed, tested, and the issue persisted. (With no extensions showing up under @installed)
@MJJBennett
Copy link
Author

It appears that this bug also occurs in CLion's integrated terminal, which leads me to believe it might be a bug with whatever system is used to create integrated terminals on Windows 10. Feel free to close this issue if this indicates it's not something that Visual Studio Code could fix.

@Tyriar
Copy link
Member

Tyriar commented Mar 19, 2018

I think this is the same root cause as #42847

@Tyriar Tyriar closed this as completed Mar 19, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 19, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants