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

Watcher crashes when large folder has lots of changes #29711

Closed
isidorn opened this issue Jun 28, 2017 · 7 comments
Closed

Watcher crashes when large folder has lots of changes #29711

isidorn opened this issue Jun 28, 2017 · 7 comments
Assignees
Labels
file-watcher File watcher help wanted Issues identified as good community contribution opportunities info-needed Issue requires more information from poster linux Issues with VS Code on Linux upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone

Comments

@isidorn
Copy link
Contributor

isidorn commented Jun 28, 2017

Refs: #29478
Linux Ubuntu 14, vscode 64 bit

  1. Clonse vscode, electron, open both repositories in VS Code
  2. while VS Code is open do a npm install in electron, and then a scripts/npm.sh i in vscode
  3. I see the file watcher crashing and all file events after that are ignored for the second repository

Do we have file watcher per repo? If yes then it seems like in this case the file watcher for repository vscode crashed. Could we detect a crash and just restart it?

screen shot 2017-06-28 at 09 38 10

@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label Jun 28, 2017
@Tyriar Tyriar added the file-watcher File watcher label Jun 28, 2017
@Tyriar Tyriar added this to the July 2017 milestone Jun 28, 2017
@Tyriar
Copy link
Member

Tyriar commented Jul 20, 2017

Cannot repro on macOS, will have to try on Linux.

@isidorn did you increase your watch limit as in https://code.visualstudio.com/docs/setup/linux#_error-enospc?

@Tyriar Tyriar added the linux Issues with VS Code on Linux label Jul 20, 2017
@isidorn
Copy link
Contributor Author

isidorn commented Jul 21, 2017

@Tyriar yes, I increased it to 524288

@bpasero
Copy link
Member

bpasero commented Jul 21, 2017

It would be nice if this limit could be set per-process and actually by the watcher process itself. Not sure that is possible though.

@Tyriar
Copy link
Member

Tyriar commented Jul 21, 2017

I think it's a system-wide limit and you need sudo to be able to set it, so we can't really do it on our side AFAIK.

@bpasero
Copy link
Member

bpasero commented Jul 21, 2017

Yeah, sucks. I was always hoping that process.setFdLimit(maxDescriptors) could be used to set it higher, but it will never be higher than the system limit it seems.

@Tyriar Tyriar modified the milestones: July 2017, August 2017 Jul 31, 2017
@Tyriar Tyriar modified the milestones: August 2017, Backlog Aug 28, 2017
@bpasero bpasero added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Sep 11, 2018
@Tyriar Tyriar added the help wanted Issues identified as good community contribution opportunities label Sep 12, 2018
@Tyriar Tyriar removed the bug Issue identified by VS Code Team member as probable bug label Oct 10, 2019
@bpasero bpasero added the info-needed Issue requires more information from poster label Sep 22, 2021
@bpasero
Copy link
Member

bpasero commented Sep 22, 2021

This bug is quite old and we have since then updated to a newer version of nsfw. I cannot reproduce, on Ubuntu 20 at least. I suggest we close this. I also didn't see this reported from other users.

@github-actions github-actions bot locked and limited conversation to collaborators Nov 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
file-watcher File watcher help wanted Issues identified as good community contribution opportunities info-needed Issue requires more information from poster linux Issues with VS Code on Linux upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

4 participants
@bpasero @isidorn @Tyriar and others