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

Running npm commands freeze the IDE #2608

Closed
slemeur opened this issue Sep 27, 2016 · 3 comments
Closed

Running npm commands freeze the IDE #2608

slemeur opened this issue Sep 27, 2016 · 3 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Milestone

Comments

@slemeur
Copy link
Contributor

slemeur commented Sep 27, 2016

Running npm commands freeze the IDE.

While doing an 'npm install' a lot of dependencies are retrieved and new files created inside of the workspaces. The IDE is triggering those file changes and trying to re-index the content of the workspace.

This behavior is freezing the IDE impacting the performances.
It basically makes the product not usable for a NodeJS project.

Discussed with @dkuleshov , it seems a side effect of the file watcher components. I believe this can be reproduced with other tools and in other situations where a lot of new files are created/modified in the workspace.

See the attached videos.

ide-freeze-npm-install-small.mp4 2.zip

Reproduction Steps:

  1. Create a workspace, using the stack https://hub.docker.com/r/codenvy/debian_jdk8_node/
  2. Import a sample NodeJS project 'https://github.com/jhipster/jhipster-sample-app'
  3. Open a terminal, go into the project folder and execute the command 'npm install'

Che version: 5.0.0-M3
Che install: beta.codenvy.com, but true with Che as well.

Additional information:

  • Problem started happening recently, didn't happen in an older version of Che: Yes
  • Problem can be reliably reproduced, doesn't happen randomly: Yes
@slemeur slemeur added kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Sep 27, 2016
@bmicklea bmicklea modified the milestone: 5.0.0-M4 Sep 27, 2016
@bmicklea bmicklea added sprint/next and removed severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Sep 27, 2016
@bmicklea
Copy link

@vparfonov please investigate whether there's a workaround that can be used to get people past this.

@dkulieshov dkulieshov added the status/in-progress This issue has been taken by an engineer and is under active development. label Sep 29, 2016
@vparfonov
Copy link
Contributor

@bmicklea we found workaround which allows to fix this specific problem, but looks like its challenge that require more time for investigation

@bmicklea
Copy link

bmicklea commented Oct 4, 2016

@vparfonov so this will continue in the next sprint?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

No branches or pull requests

4 participants