I received the topic error when starting the react app in the VS Code terminal. I have seen the answers to the topic questions as below.

Temporary Fix: $ sudo sysctl fs.inotify.max_user_watches=524288

$ sudo sysctl -p

Permanent Fix: $ echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf

$ sudo sysctl -p

1. What actually causes this error? Because I got this when tried to run the app on the next day, which I already ran it yesterday without any problem with the same files?
2. Is it possible to occur this other than node modules in Ubuntu?
3. If we set this figure, it consumes memory. Is it possible to revert it back to default 8192 again? If not possible, is it limitation in Ubuntu, which need to be addressed in future releases?

2 Answers

1. See this answer on stackexchange (not mine)

I suspect the watches from the previous day are still in effect.

2. It can happen anytime you run out of instances or watches. See previous link. User Oligofren's script and explaination is excellent.

3. Killing the watching process should work. On my machine exiting VS Code freed up ~470 watches.

from :

do this:

sudo sh -c "echo fs.inotify.max_user_watches=524288 >> /etc/sysctl.conf"
sudo sysctl -p

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password Submit

Post as a guest

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy