Skip to content

A busy stream maxes out CPU due to constant refreshes #127

@Tyriar

Description

@Tyriar

Steps to reproduce:

  1. npm start, load in browser
  2. Run ls -lR /usr/share on Linux, ls -lR /Applications on Mac (or some other big dir)
  3. View process CPU%

I believe this is happening because refresh is called at a faster rate than it takes to run.

See microsoft/vscode#7484 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions