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

In integrated terminal, setInterval console.log does not show up at correct time #112313

Closed
Arichy opened this issue Dec 11, 2020 · 5 comments
Closed

In integrated terminal, setInterval console.log does not show up at correct time #112313

Arichy opened this issue Dec 11, 2020 · 5 comments
Assignees
@Tyriar @meganrogge
Labels
info-needed Issue requires more information from poster *out-of-scope Posted issue is not in scope of VS Code terminal Integrated terminal issues
Milestone
Backlog

Comments

@Arichy
Copy link

Arichy commented Dec 11, 2020

I write a very simple demo to show the bug.

Kapture 2020-12-12 at 2 02 24

You can see it. Node correctly logs a number per second, but in vscode integrated terminal, the second console.log shows up a little late.
@meganrogge meganrogge added the terminal Integrated terminal issues label Dec 11, 2020
@meganrogge
Copy link
Contributor

Did this start happening recently? What version of VS code are you using? What are your terminal settings?

@meganrogge meganrogge added the info-needed Issue requires more information from poster label Dec 11, 2020
@Arichy
Copy link
Author

Arichy commented Dec 12, 2020

Did this start happening recently? What version of VS code are you using? What are your terminal settings?

I'm not sure when did this start.
The version of vscode is 1.52.0.
My custom terminal settings are

  "terminal.external.osxExec": "iTerm.app",
  "terminal.explorerKind": "external",
  "terminal.integrated.fontFamily": "Meslo LG M for Powerline",
  "terminal.integrated.fontSize": 13,
  "terminal.integrated.cursorBlinking": true,

The other terminal settings are all default.

@meganrogge meganrogge removed the info-needed Issue requires more information from poster label Dec 14, 2020
@meganrogge meganrogge added the bug Issue identified by VS Code Team member as probable bug label Jan 27, 2021
@meganrogge meganrogge added this to the Backlog milestone Jan 27, 2021
@meganrogge
Copy link
Contributor

does this reproduce in an external terminal?

@meganrogge meganrogge added info-needed Issue requires more information from poster and removed bug Issue identified by VS Code Team member as probable bug labels Oct 7, 2021
@Tyriar
Copy link
Member

Tyriar commented Oct 12, 2021

There was probably just a spike of CPU activity of a temporary slowdown in something when transporting the terminal data, node probably still ran it once a second. Nothing we can do here.

@Tyriar Tyriar closed this as completed Oct 12, 2021
@Tyriar Tyriar added the *out-of-scope Posted issue is not in scope of VS Code label Oct 12, 2021
@Arichy
Copy link
Author

Arichy commented Oct 12, 2021

All right. It does not reproduce now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Tyriar Tyriar

@meganrogge meganrogge

Labels
info-needed Issue requires more information from poster *out-of-scope Posted issue is not in scope of VS Code terminal Integrated terminal issues
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@Tyriar @meganrogge @Arichy